Network management systems for use with physical layer information

ABSTRACT

One exemplary embodiment is directed to a network management system that uses physical layer information in performing a network management function. Another exemplary embodiment is directed to a method of tracking channel compliance using physical layer information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication Ser. No. 61/152,624, filed Feb. 13, 2009, which is herebyincorporated herein by reference.

BACKGROUND

Communication networks typically include numerous logical communicationlinks between various items of equipment. Often a single logicalcommunication link is implemented using several pieces of physicalcommunication media. For example, a logical communication link between acomputer and an inter-networking device such as a hub or router can beimplemented as follows. A first cable connects the computer to a jackmounted in a wall. A second cable connects the wall-mounted jack to aport of a patch panel, and a third cable connects the inter-networkingdevice to another port of a patch panel. A “patch cord” cross connectsthe two together. In other words, a single logical communication link isoften implemented using several segments of physical communicationmedia.

A network or enterprise management system (generally referred to here asa “network management system” or “NMS”) is typically aware of thelogical communication links that exist in a network but typically doesnot have information about the specific physical layer media that areused to implement the logical communication links. Indeed, NMS systemstypically do not have the ability to display or otherwise provideinformation about how logical communication links are implemented at thephysical layer level.

Physical layer management (PLM) systems do exist. However, existing PLMsystems are typically designed to facilitate the adding, changing, andremoving of cross connections at a particular patch panel or a set ofpatch panels at a given location. Generally, such PLM systems includefunctionality to track what is connected to each port of a patch panel,trace connections that are made using a patch panel, and provide visualindications to a user at a patch panel. However, such PLM systems aretypically “patch-panel” centric in that they are focused on helping atechnician correctly add, change, or remove cross connections at a patchpanel. Any “intelligence” included in or coupled to the patch panel istypically only designed to facilitate making accurate cross connectionsat the patch panel and trouble shooting related problems (for example,by detecting whether a patch cord is inserted into a given port and/orby determining which ports are coupled to one another using a patchcord).

Moreover, any information that such PLM systems collect is typicallyonly used within the PLM systems. In other words, the collections ofinformation that such PLM systems maintain are logical “islands” thatare not used at the application-layer level by other systems. Thoughsuch PLM systems are sometimes connected to other networks (for example,connected to local area networks or the Internet), such networkconnections are typically only used to enable a user to remotely accessthe PLM systems. That is, a user remotely accesses the PLM-relatedapplication-layer functionality that resides in the PLM system itselfusing the external network connection but external systems or networkstypically do not themselves include any application-layer functionalitythat makes use of any of the physical-layer-related information thatresides in the PLM system.

SUMMARY

One exemplary embodiment is directed to a network management system(NMS) comprising an interface to communicatively couple the NMS to anetwork and a programmable processor configured to execute software. Thesoftware comprises physical layer information (PLI) functionality thatreceives physical layer information. The NMS uses at least a portion ofthe physical layer information in performing a network managementfunction. At least a portion of the physical layer information was readfrom a storage device included in or on physical communication media.

Another exemplary embodiment is directed to a method that is performedwhen a channel has been certified as complying with at least one channelspecification. The method includes receiving information about thecompliance of components used to implement the channel with at least onecomponent specification and receiving information about the complianceof a permanent link used to implement the channel with at least onepermanent link specification. The method further includes receivinginformation about the compliance of the channel with the at least onechannel specification and determining, using physical layer informationassociated with the components used to implement the channel at thattime, if the basis for the channel being certified as being incompliance with the at least one channel specification has changed sincewhen the channel was certified as being in compliance with the at leastone channel. The physical layer information associated with thecomponents used to implement the channel at that time includesinformation stored on or in the component that identifies thecomponents.

The details of various embodiments of the claimed invention are setforth in the accompanying drawings and the description below. Otherfeatures and advantages will become apparent from the description, thedrawings, and the claims.

DRAWINGS

FIG. 1 is a block diagram of one exemplary embodiment of a system thatincludes physical layer information (PLI) functionality as well asphysical layer management (PLM) functionality.

FIG. 2 is a block diagram of one high-level embodiment of a port andmedia reading interface that are suitable for use in the system of FIG.1.

FIG. 3 illustrates one exemplary embodiment of a system that includesphysical layer information (PLI) functionality as well as physical layermanagement (PLM) functionality.

FIG. 4 is a block diagram of one exemplary embodiment of each slaveprocessor module shown in FIG. 3.

FIG. 5 is a block diagram of one embodiment of the master processor unitof FIG. 3.

FIG. 6 is a diagram illustrating one embodiment of a patch cord that issuitable for use in the system of FIG. 3.

FIG. 7 is a diagram illustrating another exemplary embodiment of a patchcord that is suitable for use in the system of FIG. 3.

FIG. 8 is a block diagram of one embodiment of an aggregation point.

FIG. 9 is a block diagram of one embodiment of a network managementsystem (NMS) that is specially configured to use the physical layerinformation that is captured and aggregated using the techniquesdescribed here.

FIG. 10 is a flow diagram of one exemplary embodiment of a method ofcompliance tracking in a network that includes the physical layerinformation functionality.

FIG. 11 is a block diagram of one embodiment of an inter-networkingdevice that is specially configured to use physical layer informationthat is captured and aggregated using the techniques described here.

FIG. 12 illustrates an example of how physical layer information that iscaptured and aggregated using the techniques described here can be usedto improve the efficiency of the inter-networking devices used in anetwork.

FIG. 13 illustrates another exemplary embodiment of a system thatincludes physical layer information functionality as well as physicallayer management functionality.

FIGS. 14-16 illustrate another exemplary embodiment of a system thatincludes physical layer information functionality as well as physicallayer management functionality.

FIG. 17 is a block diagram of one embodiment of a wall outlet thatincludes functionality to obtain physical layer information.

FIG. 18 is one embodiment of a computer that includes functionality toobtain physical layer information.

FIG. 19 is a block diagram of one exemplary embodiment of a switch thatuses a physical layer device that includes integrated functionality forreading media information.

FIG. 20 is a block diagram of one exemplary embodiment of a computerthat uses a physical layer device that includes integrated functionalityfor reading media information.

FIG. 21 is a diagram of one embodiment of a jacket that can be fittedaround an RJ-45 plug in order to attach a storage device to the RJ-45plug.

FIG. 22 illustrates a network deploying passive fiber optic lines.

FIG. 23 is a schematic diagram showing an example cable routing schemefor the fiber distribution hubs of FIG. 23.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of one embodiment of a system 100 thatincludes physical layer information (PLI) functionality as well asphysical layer management (PLM) functionality. The system 100 comprisesa plurality of connector assemblies 102, where each connector assembly102 comprises one or more ports 104. In general, the connectorassemblies 102 are used to attach segments of physical communicationmedia to one another.

Each segment of physical communication media is attached to a respectiveport 104. Each port 104 is used to connect two or more segments ofphysical communication media to one another (for example, to implement aportion of a logical communication link). Examples of connectorassemblies 102 include, for example, rack-mounted connector assemblies(such as patch panels, distribution units, and media converters forfiber and copper physical communication media), wall-mounted connectorassemblies (such as boxes, jacks, outlets, and media converters forfiber and copper physical communication media), and inter-networkingdevices (such as switches, routers, hubs, repeaters, gateways, andaccess points).

At least some of the connector assemblies 102 are designed for use withsegments of physical communication media that have identifier andattribute information stored in or on them. The identifier and attributeinformation is stored in or on the segment of physical communicationmedia in a manner that enables the stored information, when the segmentis attached to a port 104, to be read by a programmable processor 106associated with the connector assembly 102. Examples of information thatcan be stored in or on a segment of physical communication mediainclude, without limitation, an identifier that uniquely identifies thatparticular segment of physical communication media (similar to anETHERNET Media Access Control (MAC) address but associated with thephysical communication media and/or connector attached to the physicalcommunication media), a part number, a plug or other connector type, acable or fiber type and length, a serial number, a cable polarity, adate of manufacture, a manufacturing lot number, information about oneor more visual attributes of physical communication media or a connectorattached to the physical communication media (such as information aboutthe color or shape of the physical communication media or connector oran image of the physical communication media or connector), and otherinformation used by an Enterprise Resource Planning (ERP) system orinventory control system. In other embodiments, alternate or additionaldata is stored in or on the media segments. For example, testing ormedia quality or performance information can be stored in or on thesegment of physical communication media. The testing or media quality orperformance information, for example, can be the results of testing thatis performed when a particular segment of media is manufactured.

Also, as noted below, in some embodiments, the information stored in oron the segment of physical communication media can be updated. Forexample, the information stored in or on the segment of physicalcommunication media can be updated to include the results of testingthat is performed when a segment of physical media is installed orotherwise checked. In another example, such testing information issupplied to an aggregation point 120 and stored in a data storemaintained by the aggregation point 120 (both of which are describedbelow). In another example, the information stored in or on the segmentof physical communication media includes a count of the number of timesthat a connector (not shown) attached to a segment of physicalcommunication media has been inserted into port 104. In such an example,the count stored in or on the segment of physical communication media isupdated each time the connector is inserted into port 104. Thisinsertion count value can be used, for example, for warranty purposes(for example, to determine if the connector has been inserted more thanthe number of times specified in the warranty) or for security purposes(for example, to detect unauthorized insertions of the physicalcommunication media).

In the particular embodiment shown in FIG. 1, each of the ports 104 ofthe connector assemblies 102 comprises a respective media readinginterface 108 via which the respective programmable processor 106 isable to determine if a physical communication media segment is attachedto that port 104 and, if one is, to read the identifier and attributeinformation stored in or on the attached segment (if such information isstored therein or thereon). The programmable processor 106 associatedwith each connector assembly 102 is communicatively coupled to each ofthe media reading interfaces 108 using a suitable bus or otherinterconnect (not shown).

In the particular embodiment shown in FIG. 1, four exemplary types ofconnector assembly configurations are shown. In the first connectorassembly configuration 110 shown in FIG. 1, each connector assembly 102includes its own respective programmable processor 106 and its ownrespective network interface 116 that is used to communicatively couplethat connector assembly 102 to an Internet Protocol (IP) network 118.

In the second type of connector assembly configuration 112, a group ofconnector assemblies 102 are physically located near each other (forexample, in a bay or equipment closet). Each of the connector assemblies102 in the group includes its own respective programmable processor 106.However, in the second connector assembly configuration 112, some of theconnector assemblies 102 (referred to here as “interfaced connectorassemblies”) include their own respective network interfaces 116 whilesome of the connector assemblies 102 (referred to here as“non-interfaced connector assemblies”) do not. The non-interfacedconnector assemblies 102 are communicatively coupled to one or more ofthe interfaced connector assemblies 102 in the group via localconnections. In this way, the non-interfaced connector assemblies 102are communicatively coupled to the IP network 118 via the networkinterface 116 included in one or more of the interfaced connectorassemblies 102 in the group. In the second type of connector assemblyconfiguration 112, the total number of network interfaces 116 used tocouple the connector assemblies 102 to the IP network 118 can bereduced. Moreover, in the particular embodiment shown in FIG. 1, thenon-interfaced connector assemblies 102 are connected to the interfacedconnector assembly 102 using a daisy chain topology (though othertopologies can be used in other implementations and embodiments).

In the third type of connector assembly configuration 114, a group ofconnector assemblies 102 are physically located near each other (forexample, within a bay or equipment closet). Some of the connectorassemblies 102 in the group (also referred to here as “master” connectorassemblies 102) include both their own programmable processors 106 andnetwork interfaces 116, while some of the connector assemblies 102 (alsoreferred to here as “slave” connector assemblies 102) do not includetheir own programmable processors 106 or network interfaces 116. Each ofthe slave connector assemblies 102 is communicatively coupled to one ormore of the master connector assemblies 102 in the group via one or morelocal connections. The programmable processor 106 in each of the masterconnector assemblies 102 is able to carry out the processing describedbelow for both the master connector assembly 102 of which it is a partand any slave connector assemblies 102 to which the master connectorassembly 102 is connected via the local connections. As a result, thecost associated with the slave connector assemblies 102 can be reduced.In the particular embodiment shown in FIG. 1, the slave connectorassemblies 102 are connected to a master connector assembly 102 in astar topology (though other topologies can be used in otherimplementations and embodiments).

Each programmable processor 106 is configured to execute software orfirmware that causes the programmable processor 106 to carry out variousfunctions described below. Each programmable processor 106 also includessuitable memory (not shown) that is coupled to the programmableprocessor 106 for storing program instructions and data. In general, theprogrammable processor 106 determines if a physical communication mediasegment is attached to a port 104 with which that processor 106 isassociated and, if one is, to read the identifier and attributeinformation stored in or on the attached physical communication mediasegment (if the segment includes such information stored therein orthereon) using the associated media reading interface 108.

In the first, second, and third configurations 110, 112, and 114, eachprogrammable processor 106 is also configured to communicate physicallayer information to devices that are coupled to the IP network 118. Thephysical layer information (PLI) includes information about theconnector assemblies 102 associated with that programmable processor 106(also referred to here as “device information”) as well as informationabout any segments of physical media attached to the ports 104 of thoseconnector assemblies 102 (also referred to here as “media information”)The device information includes, for example, an identifier for eachconnector assembly, a type identifier that identifies the connectorassembly's type, and port priority information that associates apriority level with each port. The media information includes identityand attribute information that the programmable processor 106 has readfrom attached physical media segments that have identifier and attributeinformation stored in or on it. The media information may also includeinformation about physical communication media that does not haveidentifier or attribute information stored in or on it. This latter typeof media information can be manually input at the time the associatedphysical media segments are attached to the connector assembly 102 (forexample, using a management application executing on the programmableprocessor 106 that enables a user to configure and monitor the connectorassembly 102).

In the fourth type of connector assembly configuration 115, a group ofconnector assemblies 102 are housed within a common chassis or otherenclosure. Each of the connector assemblies 102 in the configuration 115includes their own programmable processors 106. In the context of thisconfiguration 115, the programmable processors 106 in each of theconnector assemblies are “slave” processors 106. Each of the slaveprogrammable processor 106 is also communicatively coupled to a common“master” programmable processor 117 (for example, over a backplaneincluded in the chassis or enclosure). The master programmable processor117 is coupled to a network interface 116 that is used tocommunicatively couple the master programmable processor 117 to the IPnetwork 118. In this configuration 115, each slave programmableprocessor 106 is configured to determine if physical communication mediasegments are attached to its port 104 and to read the identifier andattribute information stored in or on the attached physicalcommunication media segments (if the attached segments have suchinformation stored therein or thereon) using the associated mediareading interfaces 108. This information is communicated from the slaveprogrammable processor 106 in each of the connector assemblies 102 inthe chassis to the master processor 117. The master processor 117 isconfigured to handle the processing associated with communicating thephysical layer information read from by the slave processors 106 todevices that are coupled to the IP network 118.

The system 100 includes functionality that enables the physical layerinformation that the connector assemblies 102 capture to be used byapplication-layer functionality outside of the traditionalphysical-layer management application domain. That is, the physicallayer information is not retained in a PLM “island” used only for PLMpurposes but is instead made available to other applications. In theparticular embodiment shown in FIG. 1, the system 100 includes anaggregation point 120 that is communicatively coupled to the connectorassemblies 102 via the IP network 118.

The aggregation point 120 includes functionality that obtains physicallayer information from the connector assemblies 102 (and other devices)and stores the physical layer information in a data store.

The aggregation point 120 can be used to receive physical layerinformation from various types of connector assemblies 106 that havefunctionality for automatically reading information stored in or on thesegment of physical communication media. Examples of such connectorassemblies 106 are noted above. Also, the aggregation point 120 andaggregation functionality 124 can also be used to receive physical layerinformation from other types of devices that have functionality forautomatically reading information stored in or on the segment ofphysical communication media. Examples of such devices include end-userdevices—such as computers, peripherals (such as printers, copiers,storage devices, and scanners), and IP telephones—that includefunctionality for automatically reading information stored in or on thesegment of physical communication media.

The aggregation point 120 can also be used to obtain other types ofphysical layer information. For example, in this embodiment, theaggregation point 120 also obtains information about physicalcommunication media segments that is not otherwise automaticallycommunicated to an aggregation point 120. One example of suchinformation is information about non-connectorized physicalcommunication media segments that do not otherwise have informationstored in or on them that are attached to a connector assembly(including, for example, information indicating which ports of thedevices are connected to which ports of other devices in the network aswell as media information about the segment). Another example of suchinformation is information about physical communication media segmentsthat are connected to devices that are not be able to read mediainformation that is stored in or on the media segments that are attachedto their ports and/or that are not able to communicate such informationto the aggregation point 120 (for example, because such devices do notinclude such functionality, because such devices are used with mediasegments that do not have media information stored in or on them, and/orbecause bandwidth is not available for communicating such information tothe aggregation point 120). In this example, the information caninclude, for example, information about the devices themselves (such asthe devices' MAC addresses and IP addresses if assigned to suchdevices), information indicating which ports of the devices areconnected to which ports of other devices in the network (for example,other connector assemblies), and information about the physical mediaattached to the ports of the devices. This information can be providedto the aggregation point 120, for example, by manually entering suchinformation into a file (such as a spreadsheet) and then uploading thefile to the aggregation point 120 (for example, using a web browser) inconnection with the initial installation of each of the various items.Such information can also, for example, be directly entered using a userinterface provided by the aggregation point 120 (for example, using aweb browser).

The aggregation point 120 can also obtain information about the layoutof the building or buildings in which the network is deployed, as wellas information indicating where each connector assembly 102, physicalmedia segment, and inter-networking device is located within thebuilding. This information can be, for example, manually entered andverified (for example, using a web browser) in connection with theinitial installation of each of the various items. In oneimplementation, such location information includes an X, Y, and Zlocation for each port or other termination point for each physicalcommunication media segment (for example, X, Y, and Z locationinformation of the type specified in the ANSI/TIA/EIA 606-A Standard(Administration Standard For The Commercial TelecommunicationsInfrastructure)).

The aggregation point 120 can obtain and maintain testing, mediaquality, or performance information relating to the various segments ofphysical communication media that exist in the network. The testing,media quality, or performance information, for example, can be resultsof testing that is performed when a particular segment of media ismanufactured and/or when testing is performed when a particular segmentof media is installed or otherwise checked.

The aggregation point 120 also includes functionality that provides aninterface for external devices or entities to access the physical layerinformation maintained by the aggregation point 120. This access caninclude retrieving information from the aggregation point 120 as well assupplying information to the aggregation point 120. In this embodiment,the aggregation point 120 is implemented as “middleware” that is able toprovide such external devices and entities with transparent andconvenient access to the PLI maintained by the access point 120. Becausethe aggregation point 120 aggregates PLI from the relevant devices onthe IP network 118 and provides external devices and entities withaccess to such PLI, the external devices and entities do not need toindividually interact with all of the devices in the IP network 118 thatprovide PLI, nor do such devices need to have the capacity to respond torequests from such external devices and entities.

The aggregation point 120, in the embodiment shown in FIG. 1, implementsan application programming interface (API) by which application-layerfunctionality can gain access to the physical layer informationmaintained by the aggregation point 120 using a software development kit(SDK) that describes and documents the API.

For example, as shown in FIG. 1, a network management system (NMS) 130includes physical layer information (PLI) functionality 132 that isconfigured to retrieve physical layer information from the aggregationpoint 120 and provide it to the other parts of the NMS 130 for usethereby. The NMS 130 uses the retrieved physical layer information toperform one or more network management functions (for example, asdescribed below). In one implementation of the embodiment shown in FIG.1, the PLI functionality 132 of the NMS 130 retrieves physical layerinformation from the aggregation point 120 using the API implemented bythe aggregation point 120. The NMS 130 communicates with the aggregationpoint 120 over the IP network 118.

As shown in FIG. 1, an application 134 executing on a computer 136 canalso use the API implemented by the aggregation point 120 to access thePLI information maintained by the aggregation point 120 (for example, toretrieve such information from the aggregation point 120 and/or tosupply such information to the aggregation point 120). The computer 136is coupled to the IP network 118 and accesses the aggregation point 120over the IP network 118.

In the embodiment shown in FIG. 1, one or more inter-networking devices138 used to implement the IP network 118 include physical layerinformation (PLI) functionality 140. The PLI functionality 140 of theinter-networking device 138 is configured to retrieve physical layerinformation from the aggregation point 120 and use the retrievedphysical layer information to perform one or more inter-networkingfunctions. Examples of inter-networking functions include Layer 1, Layer2, and Layer 3 (of the OSI model) inter-networking functions such as therouting, switching, repeating, bridging, and grooming of communicationtraffic that is received at the inter-networking device. In oneimplementation of such an embodiment, the PLI functionality 140 uses theAPI implemented by the aggregation point 120 to communicate with theaggregation point 120.

The PLI functionality 140 included in the inter-networking device 138can also be used to capture physical layer information associated withthe inter-network device 138 and the physical communication mediaattached to it and communicate the captured physical layer informationto the aggregation point 120. Such information can be provided to theaggregation point 120 using the API or by using the protocols that areused to communicate with the connector assemblies 102.

The aggregation point 120 can be implemented on a standalone networknode (for example, a standalone computer running appropriate software)or can be integrated along with other network functionality (forexample, integrated with an element management system or networkmanagement system or other network server or network element). Moreover,the functionality of the aggregation point 120 can be distribute acrossmany nodes and devices in the network and/or implemented, for example,in a hierarchical manner (for example, with many levels of aggregationpoints).

Moreover, the aggregation point 120 and the connector assemblies 102 areconfigured so that the aggregation point 120 can automatically discoverand connect with devices that provide PLI to an aggregation point 120(such as the connector assemblies 102 and inter-network device 138) thatare on the network 118. In this way, when devices that are able toprovide PLI to an aggregation point 120 (such as a connector assembly102 or an inter-networking device 138) are coupled to the IP network118, an aggregation point 120 is able to automatically discover theconnector assembly 102 and start aggregating physical layer informationfor that connector assembly 102 without requiring the person installingthe connector assembly 102 to have knowledge of the aggregation points120 that are on the IP network. Similarly, when an aggregation point 120is coupled to the IP network 118, the aggregation point 120 is able toautomatically discover and interact with devices that are capable ofproviding PLI to an aggregation point without requiring the personinstalling the aggregation point 120 to have knowledge of the devicesthat are on the IP network 118. Thus, the physical-layer informationresources described here can be easily integrated into the IP network118.

The IP network 118 can include one or more local area networks and/orwide area networks (including for example the Internet). As a result,the aggregation point 120, NMS 130, and computer 136 need not be locatedat the same site as each other or at the same site as the connectorassemblies 102 or the inter-networking devices 138.

Various conventional IP networking techniques can be used in deployingthe system 100 of FIG. 1. For example, conventional security protocolscan be used to secure communications if they are communicated over apublic or otherwise unsecure communication channel (such as the Internetor over a wireless communication link).

In one implementation of the embodiment shown in FIG. 1, each connectorassembly 102, each port 104 of each connector assembly 102, and eachmedia segment is individually addressable. Where IP addresses are usedto individually address each connector assembly 102, a virtual privatenetwork (VPN) dedicated for use with the various connector assemblies102 can be used to segregate the IP addresses used for the connectorassemblies 102 from the main IP address space that is used in the IPnetwork 118.

Also, power can be supplied to the connector assemblies 102 usingconventional “Power over Ethernet” techniques specified in the IEEE802.3af standard, which is hereby incorporated herein by reference. Insuch an implementation, a power hub 142 or other power supplying device(located near or incorporated into an inter-networking device that iscoupled to each connector assembly 102) injects DC power onto one ormore of the wires (also referred to here as the “power wires”) includedin the copper twisted-pair cable used to connect each connector assembly102 to the associated inter-networking device. The interface 116 in theconnector assembly 102 picks the injected DC power off of the powerwires and uses the picked-off power to power the active components ofthat connector assembly 102. In the second and third connector assemblyconfigurations 112 and 114, some of the connector assemblies 102 are notdirectly connected to the IP network 118 and, therefore, are unable toreceive power directly from the power wires. These connector assemblies102 receive power from the connector assemblies 102 that are directlyconnected to the IP network 118 via the local connections thatcommunicatively such connector assemblies 102 to one another. In thefourth configuration 115, the interface 116 picks the injected DC poweroff of the power wires and supplies power to the master processor 117and each of the slave processors 106 over the backplane.

In the particular embodiment shown in FIG. 1, the system 100 alsosupports conventional physical layer management (PLM) operations such asthe tracking of moves, adds, and changes of the segments of physicalmedia that are attached to the ports 104 of the connector assemblies 102and providing assistance with carrying out moves, adds, and changes. PLIprovided by the aggregation point 120 can be used to improve uponconventional “guided MAC” processes. For example, information about thelocation of the port 104 and the visual appearance (for example, thecolor or shape) of the relevant physical media segment (or connectorattached thereto) can be communicated to a technician to assist thetechnician in carrying out a move, add, or change. This information canbe communicated to a computer or smartphone used by the technician.Moreover, the PLI functionality that resides in the system 100 can alsobe used to verify that a particular MAC was properly carried out bychecking that the expected physical media segment is located in theexpected port 104. If that is not the case, an alert can be sent to thetechnician so that the technician can correct the issue.

The PLM functionality included in the system 100 can also supportconventional techniques for guiding the technician in carrying out a MAC(for example, by illuminating one or more light emitting diodes (LEDs)to direct a technician to a particular connector assembly 102 and/or toa particular port 104 or by displaying messages on a liquid crystaldisplay (LCD) included on or near the connector assemblies 102.

Other PLM functions include keeping historical logs about the mediaconnected to the connector assembly. In the embodiment shown in FIG. 1,the aggregation point 120 includes PLM functionality 144 that implementssuch PLM functions. The PLM functionality 144 does this using thephysical layer information that is maintained at the aggregation point120.

The IP network 118 is typically implemented using one or moreinter-networking devices. As noted above, an inter-networking device isa type of connector assembly (and a particular implementation of aninter-networking device 138 is referenced separately in FIG. 1 for easeof explanation only). Generally, an inter-networking device can beconfigured to read media information that is stored in or on thesegments of physical media that are attached to its ports and tocommunicate the media information it reads from the attached segments ofmedia (as well as information about the inter-networking device itself)to an aggregation point 120 like any other connector assembly describedhere.

In addition to connector assemblies 102, the techniques described herefor reading media information stored in or on a segment of physicalcommunication media can be used in one or more end nodes of the network.For example, computers (such as, laptops, servers, desktop computers, orspecial-purpose computing devices such as IP telephones, IP multi-mediaappliances, and storage devices) can be configured to read mediainformation that is stored in or on the segments of physicalcommunication media that are attached to their ports and to communicatethe media information the read from the attached segments of media (aswell as information about the devices themselves) to an aggregationpoint 120 as described here.

FIG. 2 is a block diagram of one high-level embodiment of a port 104 andmedia reading interface 106 that are suitable for use in the system 100of FIG. 1.

Each port 104 comprises a first attachment point 206 and a secondattachment point 208. The first attachment point 206 is used to attach afirst segment of physical communication media 210 to the port 104, andthe second attachment point 208 is used to attach a second segment ofphysical communication media 212 to the port 104.

In the particular embodiment shown in FIG. 2, the first attachment point206 is located near the rear of the connector assembly. As aconsequence, the first attachment point 206 and the first segment ofphysical media 210 attached thereto are also referred to here as the“rear attachment point” 206 and the “rear media segment” 210,respectively. Also, in this embodiment, the rear attachment point 206 isconfigured to attach the rear media segment 210 to the port 104 in asemi-permanent manner. As used herein, a semi-permanent attachment isone that is designed to be changed relatively infrequently, if ever.This is also referred to sometimes as a “one-time” connection. Examplesof suitable rear connectors 206 include punch-down blocks (in the caseof copper physical media) and fiber adapters, fiber splice points, andfiber termination points (in the case of optical physical media).

In the embodiment shown in FIG. 2, the second attachment point 208 islocated near the front of the connector assembly 102. As a consequence,the second attachment point 208 and the second segment of physical media212 are also referred to here as the “front attachment point” 208 andthe “front media segment” 212, respectively. In the embodiment shown inFIG. 2, the front attachment point 208 for each port 104 is designed foruse with “connectorized” front media segments 212 that have identifierand attribute information stored in or on them. As used herein, a“connectorized” media segment is a segment of physical communicationmedia that includes a connector 214 at at least one end of the segment.The front attachment point 208 is implemented using a suitable connectoror adapter that mates with the corresponding connector 214 on the end ofthe front media segment 212. The connector 214 is used to facilitate theeasy and repeated attachment and unattachment of the front media segment212 to the port 104. Examples of connectorized media segments includeCAT-5, 6, and 7 twisted-pair cables having modular connectors or plugsattached to both ends (in which case, the front connectors areimplemented using compatible modular jacks) or optical cables having SC,LC, FC, LX.5, MTP, or MPO connectors (in which case, the frontconnectors are implemented using compatible SC, LC, FC, LX.5, MTP, orMPO connectors or adapters). The techniques described here can be usedwith other types of connectors including, for example, BNC connectors, Fconnectors, DSX jacks and plugs, bantam jacks and plugs, and MPO and MTPmulti-fiber connectors and adapters.

Each port 104 communicatively couples the respective rear attachmentpoint 206 to the respective front attachment point 208. As a result, arear media segment 210 attached to the respective rear attachment point206 is communicatively coupled to any front media segment 212 attachedto the respective front attachment point 208. In one implementation,each port 104 is designed for use with a rear media segment 210 and afront media segment 212 that comprise the same type of physicalcommunication media, in which case each port 104 communicatively couplesany rear media segment 210 attached to the respective rear attachmentpoint 206 to any front media segment 212 attached to the respectivefront attachment point 208 at the physical layer level without any mediaconversion. In other implementations, each port 104 communicativelycouples any rear media segment 210 attached to the respective rearattachment point 206 to any front media segment 212 attached to therespective front attachment point 208 in other ways (for example, usinga media converter if the rear media segment 210 and the front mediasegment 212 comprise different types of physical communication media).

As shown in FIG. 2, the port 104 is configured for use with front mediasegments 212 that include a storage device 216 in which the mediainformation for that media segment 212 is stored. The storage device 216includes a storage device interface that, when the correspondingconnector 214 is inserted into (or otherwise attached to) a frontattachment point 208 of the port 104, communicatively couples thestorage device 216 to a corresponding media reading interface 108 sothat the associated programmable processor 106 can read the informationstored in the storage device 216. In one implementation of theembodiment shown in FIG. 2, each connector 214 itself houses the storagedevice 216. In another implementation of such an embodiment, the storagedevice 216 is housed within a housing that is separate from theconnector 214. In such an implementation, the housing is configured sothat it can be snapped onto the media segment 212 or the connector 214,with the storage device interface positioned relative to the connector214 so that the storage device interface will properly mate with themedia reading interface 108 when the connector 214 is inserted into (orotherwise attached to) the front attachment point 208.

In some implementations, at least some of the information stored in thestorage device 216 can be updated in the field (for example, by havingan associated programmable processor 106 cause additional information tobe written to the storage device 216 or changing or deleting informationthat was previously stored in the storage device 216). For example, insome implementations, some of the information stored in the storagedevice 216 cannot be changed in the field (for example, identifierinformation or manufacturing information) while some of the otherinformation stored in the storage device 216 can be changed in the field(for example, testing, media quality, or performance information). Inother implementations, none of the information stored in the storagedevice 216 can be updated in the field.

Also, the storage device 216 may also include a processor ormicro-controller, in addition to storage for the media information. Inwhich case, the micro-controller included in the storage device 216 canbe used to execute software or firmware that, for example, controls oneor more LEDs attached to the storage device 216. In another example, themicro-controller executes software or firmware that performs anintegrity test on the front media segment 212 (for example, byperforming a capacitance or impedance test on the sheathing or insulatorthat surrounds the front physical communication media segment 212,(which may include a metallic foil or metallic filler for suchpurposes)). In the event that a problem with the integrity of the frontmedia segment 212 is detected, the micro-controller can communicate thatfact to the programmable processor 106 associated with the port 104using the storage device interface (for example, by raising aninterrupt). The micro-controller can also be used for other functions.

FIG. 3 illustrates one embodiment of a system 300 that includes physicallayer information (PLI) functionality as well as physical layermanagement (PLM) functionality. The system 300 comprises a plurality ofpatch panels 302 that are housed within a common chassis 301. Forexample, in one common configuration, the chassis 301 is installed in acommunications closet or room and is mounted in a rack. In some largerinstallations, there are several racks of chassis 301 and patch panels302 (arranged, for example, in several bays). The patch panels 302 canbe packaged as blades that are slid into the chassis 301.

Each patch panel 302 comprises a set of ports 304 (for example, 16, 32,48, or 512 ports 304). The number of ports 304 can vary from patch panel302 to patch panel 302.

Each of the ports 304 is implemented as shown in FIG. 2. In general, inthe context of the embodiment shown in FIG. 3, each front media segment312 comprises a “patch cord” 312 that is used to selectivelycross-connect two ports 304 from the same or different patch panels 302.In this embodiment, each patch cord 312 has a modular plug 314 attachedto each end that can be inserted into a front media connector of one ofthe ports 304 of the patch panels 302.

In this way, respective rear media segments (not shown in FIG. 3)coupled to the two cross-connected ports 304 can be communicativelycoupled to one another in order to implement a logical communicationlink between the equipment that is coupled to the respective rear mediasegments. For example, in one exemplary application, a wall-mounted jackis communicatively coupled to a rear connector of a port 304 using asuitable rear media segment such as a copper or fiber cable. The cableis typically routed through a building (for example, over, under,around, and/or through walls, ceilings, floors, and the like) and is noteasily or frequently moved. If a first piece of equipment that isconnected to one such wall-mounted jack needs to be communicativelycoupled to a second piece of equipment that is connected to another suchwall-mounted jack, a patch cord 312 can be used to establish theconnection.

As shown in FIG. 3, a master processor unit (MPU) 330 is also housedwithin the chassis 301. The master processor unit (MPU) 330 communicateswith slave processor modules 318 included in each of the patch panels304 over a backplane 315. FIG. 4 is a block diagram of one embodiment ofeach slave processor module 318 shown in FIG. 3. Each slave processormodule 318 comprises a slave programmable processor 320 that executessoftware 322. The execution of the software 322 causes the slaveprocessor 320 to carry out various functions described below. Each slaveprocessor module 318 also includes memory 324 that is coupled to theslave processor 320 for storing program instructions and data. The slaveprocessor 320 in each slave processor module 318 is coupled to thebackplane 315 using a suitable interface.

The system 300 is designed to be used with patch cords 312 (or otherfront media segments) that have identifier and attribute information ofthe type described above in connection with FIG. 2 stored in or on them.Each of the ports 304 of each patch panel 302 comprises a respectivemedia reading interface (not shown in FIG. 3). The slave programmableprocessor 320 in each patch panel 302 is communicatively coupled to eachof the media reading interfaces in that patch panel 302 using a bus orother interconnect (not shown). The slave programmable processor 320 isconfigured to determine if the state of a port 304 changes. The state ofa port 304 changes, for example, when a patch cord is inserted into apreviously empty front connector or when a patch cord 312 is removedfrom a front connector, or when a different patch cord is inserted intoa previously occupied front connector.

In one implementation of such an embodiment, each media readinginterface is configured so that the slave programmable processor 320 candetect changes in the state of each port 304. For example, theelectrical contact structure of the media reading interface can beconfigured so that an electrical signal changes state when a patch cordis inserted into or removed from a port 304 (for example, by closing oropening an electrical circuit). The slave processor 320 detects suchstate changes to detect when a patch cord has been inserted into orremoved from the front connector of each port 304. Examples of suchcontact structures are U.S. Provisional Patent Application Ser. No.61/252,395, filed on Oct. 16, 2009, titled “MANAGED CONNECTIVITY INELECTRICAL SYSTEMS AND METHODS THEREOF” (also referred to here as the“'395 application”), U.S. Provisional Patent Application Ser. No.61/253,208, filed on Oct. 20, 2009, titled “ELECTRICAL PLUG FOR MANAGEDCONNECTIVITY SYSTEMS” (also referred to here as the “'208 application”),and U.S. Provisional Patent Application Ser. No. 61/252,964, filed onOct. 19, 2009, titled “ELECTRICAL PLUG FOR MANAGED CONNECTIVITY SYSTEMS”(also referred to here as the “'964 application”). The '395 application,the '208 application, and the '964 application are hereby incorporatedherein by reference.

Alternatively, the slave processor 320 can be configured to periodicallyscan all of the media reading interfaces included in that patch panel302 to determine if the state of any of the associated ports 304 haschanged.

Also, when the software 322 executing on the slave programmableprocessor 320 in each patch panel 302 determines that a patch cord hasbeen inserted into a previously empty front connector or that adifferent patch cord has been inserted into a previously connected frontconnector, the software 322 reads the information stored in or on theinserted patch cord.

Any changes in the state of the patch panel ports 304 and theinformation that is read from the patch cords are communicated to theMPU 330 over the backplane 315. The port state information and theinformation read from the patch cords are collectively referred to hereas “port information.”

The software 322 executing on the slave programmable processor 320 ineach patch panel 302 also communicates information about the respectivepatch panel 302 to the MPU 330 over the backplane 115 (such informationis also referred to here as “patch panel information”). The patch panelsoftware 322 communicates the patch panel information to the MPU 330,for example, in the following situations: in response to a request fromthe MPU 330, or when the patch panel 302 first powers up, or when any ofpatch panel's information changes, or after a predetermined amount oftime has elapsed since last communicating the patch panel information tothe MPU 330.

As shown in FIG. 3, each of the ports 304 of each patch panel 302includes a respective visual indicator 316 (such as a light emittingdiode (LED)) that is coupled to the slave programmable processor 318over an internal bus or other interconnect (not shown). The visualindicator 316 is located near the port 304 with which the visualindicator 316 is associated. The slave programmable processor 332 canactuate each of the visual indicators 316 (for example, by illuminatingan LED) in order to identify the associated port 304.

As shown in FIG. 3, the MPU 330 is configured to communicate with andcontrol the slave processor modules 318. Also, the MPU 330 is configuredto communicate with other devices over an IP network 350 (such as LAN352). More specifically, the MPU 330 is configured to communicate withan aggregation point 353 over the LAN 352. FIG. 5 is a block diagram ofone embodiment of the master processor unit 330 of FIG. 3. The MPU 330includes a master programmable processor 332 that executes software 334.The execution of the software 334 causes the master programmableprocessor 332 of the MPU 330 to carry out various functions describedbelow. The MPU 330 also includes memory 336 that is coupled to themaster processor 332 for storing program instructions and data. Themaster processor 332 is coupled to the backplane 315 of the chassis 301.The slave processor 320 in each of the patch panels 302 communicateswith the master programmable processor 332 in the MPU 330 over thebackplane 315. In the particular embodiment shown in FIG. 3, most of theprocessing that is performed in the system 300 is performed by themaster programmable processor 332 in the MPU 330. As a result, arelatively low power slave programmable processor 318 can be used ineach of the patch panels 302, such as an 8-bit or 16-bitmicrocontroller. The master programmable processor 332 in the MPU 330,in such an embodiment, is implemented using a 16-bit or 32-bitmicrocontroller or microprocessor.

The MPU 330 further comprises an ETHERNET interface 340 that is used tocommunicatively couple the MPU 330 (and the master programmableprocessor 332 included therein) to one or more Internet Protocol (IP)networks 350 (shown in FIG. 3). In the particular embodiment shown inFIG. 3, the ETHERNET interface 340 is coupled to a local area network(LAN) 352. This connection to the LAN 352 can be implemented, forexample, by using a cable to connect the ETHERNET interface 340 of theMPU 330 to one port 304 of a patch panel 302 (by attaching the cable tothe rear attachment point 306 of that port 304). Each of multiple portsof an inter-networking device (such as a hub, router, or switch) (notshown in FIG. 3) is also connected to respective ports 304 of a patchpanel 302 (by connecting respective cables to the respective rearattachment points 306 of the ports 304). The ETHERNET interface 340 ofthe MPU 330 is cross-connected to a port of the inter-networking deviceby inserting one end 314 of a patch cord 312 into the front connector308 of the port 304 that is connected to the ETHERNET interface 340 andby inserting the other end 314 of the patch cord 312 into the frontconnector 308 of the port 306 that is connected to one of the ports ofthe inter-networking device. The other ports of the inter-networkingdevice are connected (via the patch panels 302) to other items of enduser equipment 356 (shown in FIG. 3) (such as computers) and otherinter-networking devices (such as gateways or network interface devicesthat connect the LAN 352 to a wide area network such the Internet 358(shown in FIG. 3)).

As shown in FIG. 5, in this particular embodiment, the MPU software 334includes a TCP/IP stack 342 that enables the MPU processor 332 tocommunicate with other devices over the one or more IP networks 350.

In the embodiment shown in FIG. 3, power is supplied to the MPU 330 andthe slave processor modules 318 over the twisted-pair copper wiring thatis used to connect the MPU 330 to the LAN 352. Power is supplied usingPower over Ethernet techniques specified in the IEEE 802.3af standard.In such an embodiment, the inter-working device to which the MPU 330 iscoupled includes a power hub 354 or other power supplying device(located near or incorporated into it) that injects DC power onto one ormore of the wires (also referred to here as the “power wires”) includedin the copper twisted-pair cable used to connect the MPU 330 to theinter-networking device. The ETHERNET interface 340 in MPU 330 picks theinjected DC power off of the power wires and uses the picked-off powerto power the active components in the MPU 330. Also, power is suppliedfrom the MPU 330 to the patch panels 302 over the backplane 315 in orderto power the active components in the patch panels 302.

In the particular embodiment shown in FIG. 4, the MPU 330 also comprisesa power supply unit (PSU) 344 for situations where the devices in thechassis 301 are not powered using Power over Ethernet. The PSU 344 canbe connected to one or more external power sources 346 (shown in FIG. 3)(such as the alternating current (AC) power grid and/or a telco/datacenter direct current (DC) power source) and converts the external powerreceived from the external power source 346 to power that is suitablefor use by the active components of the MPU 330 and the patch panels302.

The MPU software 334 executing on the MPU programmable processor 332receives the port and patch panel information from all of the patchpanels 302 and maintains a data store 362 (shown in FIG. 5) in which theinformation is stored and organized. The MPU software 334 executing onthe MPU programmable processor 332 is also configured to communicatewith one or more aggregation points 353. In the particular embodimentshown in FIG. 5, the MPU software 334 includes discovery protocolsoftware 364 that is used by the MPU 330 and the aggregation point 353to discover and connect with one another. The MPU software 334 alsoincludes communication protocol software 366 that is used to communicateport and patch panel information (and other PLI) to and from theaggregation port 353.

The MPU software 334 also includes functionality that enables users,systems, and devices to directly interact with the MPU 330 over the IPnetworks 350. In the particular embodiment shown in FIGS. 3-11, the MPUsoftware 334 is configured to interact with users using a web browser.In this embodiment, the MPU software 334 includes a web server 370(shown in FIG. 5) that enables the MPU 330 to interact with a user's webbrowser over the IP networks 350 using the HyperText Markup Language(HTML) protocol (and related protocols such as the AsynchronousJavaScript and XML (AJAX) protocols). In the particular embodiment shownin FIGS. 3-11, the MPU software 334 is also configured to directlyinteract with users, systems, and devices in other ways. For example,the MPU software 334 includes TELNET software 372 that enables otherusers, systems, and devices to telnet into the MPU 330 and an emailserver 374 (implementing, for example, the Simple Mail Transfer Protocol(SMTP)) that enables the MPU software 334 to send email messages toother users, systems, and devices. The MPU software 334 also includessecurity and encryption software 376 to enable the MPU software 334 tocommunicate in a secure manner (for example, using Secure Sockets Layer(SSL) sessions or virtual private networks (VPNs)).

In the embodiment shown in FIGS. 3-11, the system 300 is configured tohave a user manually enter, for each port 304 that has a respective rearmedia segment 310 attached to its rear attachment point, informationabout the physical media that is used to implement that rear mediasegment. In this embodiment, the rear media segments are connected tothe rear attachment points in a semi-permanent manner, and typicallythese connections do not change often, if ever. As a result, informationabout the physical media used to implement the rear media segments canbe manually entered and verified in connection with the initialinstallation of the media and will typically remain valid thereafter.This information can include information similar to the port informationstored in or on a patch cord and is also referred to here as “rear mediainformation.” In the event that a change is made to the media that isattached to a rear attachment point of a port 304, the correspondingphysical media information for that port 304 would need to be manuallyupdated. This read media information, for example, can be entered into aspreadsheet or other file. The spreadsheet is then uploaded to theaggregation point 353. The aggregation point 353 associates the readmedia information included in the spreadsheet with information about thepatch panels 302 and the ports 304 that it obtains from the MPU 330.

Also, when an inter-networking device (such as a switch or router) isconnected to the rear attachment points of the ports 304 of a patchpanel 302, information about the inter-networking device (such as thedevice's MAC address and an assigned IP address) and informationindicating which port of the inter-networking device is connected towhich port 304 of the patch panel 302 can be manually entered andprovided to the aggregation point 353 in connection with the initialinstallation of the inter-networking device. This information is alsoreferred to here as “inter-networking device information.” Also, asnoted above, if the inter-networking device includes PLI functionality,such inter-networking device information can be automatically capturedby the inter-networking device and communicated to the aggregation point353.

In addition, in the embodiment shown in FIGS. 3-11, the system 300 isconfigured to have a user enter information about the layout of thebuilding or buildings in which the network is deployed, as well asinformation indicating where each patch panel 302, rear media segment,inter-networking device, and wall outlet is located within the building.This information is also referred to here as “location information”. Forexample, this location information can be entered into a spreadsheet anduploaded to the aggregation point 353, which associates the locationinformation with the other PLI it has obtained about the system 300.

In the embodiment shown in FIGS. 3-11, the aggregation point 353 hasaccess to many types of physical layer information including, forexample, device information (that is, the port information, patch panelinformation, inter-networking device information and information anywall outlets and end user devices), media information (that is, frontmedia information—including the media information stored on the patchcords—and rear media information), and location information.

In the embodiment shown in FIG. 3, the MPU 330 also includes additionalinterfaces 382 for communicatively coupling the MPU 330 (and the MPUprogrammable processor 332) to one or more external sensors (forexample, external temperature sensors) and alarms 384 (shown in FIG. 1).The MPU 330 can be communicatively coupled to such external sensors andalarms 384 using wired and/or wireless communication links. In oneapplication, a thermal map of the network can be produced fromtemperature readings, which may be useful for HVAC purposes.

Also, as shown in FIG. 5, the MPU 330 includes an interface 378 by whicha technician can directly connect a device such as a computer, personaldigital assistant (PDA), or smartphone to the MPU 330 and interact withthe software 334 executing the master processor 332.

In one implementation of the embodiment shown in FIGS. 3-11, the MPU 330and the slave processor module 318, media reading interfaces andassociated visual indicators 316 are integrated into the patch panel 302along with the other components. In another implementation, the MPU 330and the slave processor module 318, media reading interfaces andassociated visual indicators 316 are housed within one or more modulesthat are separate from the respective patch panel 302. In such animplementation, the separate modules are attached to the front of therespective patch panel 302 so that each visual indicator 316 and mediareading interface is positioned near its corresponding port 304.

In some embodiments, a display (such as a liquid crystal display) isincorporated into the MPU 330, the slave processor modules 318, or thepatch panel 302 to display messages at the patch panel 302. Also, insome embodiments, a user input mechanism (such as one or more buttons)is incorporated into the MPU 330, the slave processor modules 318, orthe patch panel 302 to receive input from a user that is located nearthe patch panels 302.

FIG. 6 is a diagram illustrating one embodiment of a patch cord 312 thatis suitable for use in the system 300 of FIG. 3. The patch cord 312shown in FIG. 6 is suitable for use with an implementation of the patchpanel 302 of FIG. 3 where the front connectors of the ports 304 areimplemented using modular RJ-45 jacks. The patch cord 312 shown in FIG.6 comprises a copper unshielded twisted-pair (UTP) cable 386. The UTPcable 386 includes eight conductors arranged in four conductor pairs.The patch cord 312 also comprises two RJ-45 plugs 314, one at each endof the cable 386 (only one of which is shown in FIG. 6). The RJ-45 plugs314 are designed to be inserted into the RJ-45 modular jacks used as thefront connectors. Each RJ-45 plug 314 comprises a contact portion 388 inwhich eight, generally parallel electrical contacts 390 are positioned.Each of the eight electrical contacts 390 are electrically connected toone of the eight conductors in the UTP cable 386.

Each plug 314 also comprises (or is attached to) a storage device 392(for example, an Electrically Erasable Programmable Read-Only Memory(EEPROM) or other non-volatile memory device). The media informationdescribed above for the patch cord 312 is stored in the storage device392. The storage device 392 includes sufficient storage capacity tostore such information. Each storage device 392 also includes a storagedevice interface 394 that, when the corresponding plug 314 is insertedinto a front connector of a port 304, communicatively couples thestorage device 392 to the corresponding media reading interface so thatthe programmable processor 320 in the corresponding patch panel 302 canread the information stored in the storage device 392.

Examples of such a patch cord 312 and plug 314 are described in the '395application, the '208 application, and the '964 application.

The embodiment shown in FIGS. 3-11 is generally described here as beingimplemented using the patch cord 312 shown in FIG. 6. However, othertypes of patch cords can be used, one of which is shown in FIG. 7.

FIG. 7 is a diagram illustrating another embodiment of a patch cord 312′that is suitable for use in the system 300 of FIG. 3. The patch cord312′ shown in FIG. 7 is suitable for use with an implementation of thepatch panel 302 of FIG. 3 where the front connectors of the ports 304are implemented using fiber LC adapters or connectors. The patch cord312′ shown in FIG. 7 comprises an optical cable 386′. The optical cable386′ includes an optical fiber enclosed within a suitable sheathing. Thepatch cord 312′ also comprises two LC connectors 314′, on at each of thecable 386′. Each LC connector 314′ is designed to be inserted into an LCadapter used as the front connector of a port 304. Each LC connector314′ comprises an end portion 388′ at which an optical connection withthe optical fiber in the cable 386′ can be established when the LCconnector 314′ is inserted in an LC adapter of a port 304.

Each LC connector 314′ also comprises (or is attached to) a storagedevice 392′ (for example, an Electrically Erasable ProgrammableRead-Only Memory (EEPROM) or other non-volatile memory device). Themedia information described above for the patch cord 312 is stored inthe storage device 392′. The storage device 392′ includes sufficientstorage capacity to store such information. Each storage device 392′also includes a storage device interface 394′ that, when thecorresponding LC connector 314′ is inserted into a front connector of aport 304, communicatively couples the storage device 392′ to thecorresponding media reading interface so that the slave programmableprocessor 320 in the corresponding patch panel 302 can read theinformation stored in the storage device 392′.

In some implementations of the patch cords 312 and 312′, the storagedevices 392 and 392′ are implemented using a surface-mount EEPROM orother non-volatile memory device. In such implementations, the storagedevice interfaces and media reading interfaces each comprise fourleads—a power lead, a ground lead, a data lead, and an extra lead thatis reserved for future use. The four leads of the storage deviceinterfaces come into electrical contact with four corresponding leads ofthe media reading interface when the corresponding plug or connector isinserted in the corresponding front connector of a port 304. Eachstorage device interface and media reading interface are arranged andconfigured so that they do not interfere with data communicated over thepatch cord. In other embodiments, other types of interfaces are used.For example, in one such alternative embodiment, a two-line interface isused with a simple charge pump. In other embodiments, additional linesare provided (for example, for potential future applications).

Examples of such fiber patch cords 312′ and connectors 314′ aredescribed in U.S. Provisional Patent Application Ser. No. 61/252,386,filed on Oct. 16, 2009, titled “MANAGED CONNECTIVITY IN FIBER OPTICSYSTEMS AND METHODS THEREOF” (also referred to here as the “'386application”), U.S. Provisional Patent Application Ser. No. 61/303,961,filed on Feb. 12, 2010, titled “FIBER PLUGS AND ADAPTERS FOR MANAGEDCONNECTIVITY” (the “'961 application”), and U.S. Provisional PatentApplication Ser. No. 61/303,948, filed on Feb. 12, 2010, titled “BLADEDCOMMUNICATIONS SYSTEM” (the “'948 application”). The '386 application,the '961 application, and the '948 application are hereby incorporatedherein by reference.

In some implementations of the patch cords 312 and 312′, each plug 314or connector 314′ itself houses the respective storage device andstorage device interface. In implementations, each storage device andcorresponding storage device interface are housed within a housing thatis separate from the corresponding plug or connector. In suchimplementations, the housing is configured so that it can be snappedonto (or otherwise attached to) the cable or the plug or connector, withthe storage device interface positioned relative to the plug orconnector so that the storage device interface will properly mate withthe relevant media reading interface when the plug or connector isinserted into the front connector of the corresponding port 304.

A hand-held test set can be provided that includes a port into which theplug 314 or connector 314′ of a patch cord 312 or 312′ can be insertedin order to read the media information stored in the storage device. Thehand-held test set also includes a display of some type to display themedia information that was read from the storage device.

In other embodiments, the storage device also includes an optical orinfrared interface for reading the media information stored in thestorage device while the corresponding patch cord 312 or 312′ isconnected to one or more patch panels 302. This enables a technician toread the media information stored in the storage device without havingto remove the patch cord 312 or 312′ in order to use the hand-heldtester described above.

The remainder of the description of the embodiment shown in FIGS. 3-11generally refers to the patch cord 312 shown in FIG. 6. However, it isto be understood that other patch cords can be used (such as the patchcord 312′ shown in FIG. 7).

FIG. 8 is a block diagram of one embodiment of an aggregation point 353.The particular embodiment of an aggregation point 353 shown in FIG. 8 isdescribed here as being implemented for use in the system 300 of FIG. 3,though other embodiments can be implemented in other ways.

The aggregation point 353 is typically implemented as software 800 thatexecutes on a workstation or other computer 802. The workstation 802comprises at least one programmable processor 804 on which the software800 executes. The software 800 comprises program instructions that arestored (or otherwise embodied) on an appropriate storage medium or mediafrom which at least a portion of the program instructions are read bythe programmable processor 804 for execution thereby. The workstation802 also comprises memory 806 for storing the program instructions andany related data during execution of the software 800.

The workstation 802 on which the aggregation point software 800 executesalso includes one or more interfaces 808 that communicatively couple theaggregation point 353 to devices or entities with which it communicates.More specifically, the one or more interfaces 808 communicatively couplethe aggregation point 353 to these devices or entities over the one ormore IP networks 350. In one implementation of such an embodiment, atleast one of the interfaces 808 comprises an ETHERNET network interfacefor coupling the aggregation point 353 to the one or more IP networks350.

The aggregation point software 800 comprises PLI aggregation software810 that enables the aggregation point 353 to automatically discover andconnect with devices that are able provide PLI and other information tothe aggregation point 353 (such as the patch panels 302). Theaggregation point 353 and the PLI aggregation software 810 can be usedto receive physical layer information from various types of connectorassemblies that have functionality for automatically reading informationstored in or on a segment of physical communication media. Examples ofsuch devices are noted above and include, for example, patch panels 302and inter-networking devices. Also, the aggregation point 353 and PLIaggregation software 810 can also be used to receive physical layerinformation from other types of devices that have functionality forautomatically reading information stored in or on the segment ofphysical communication media. Examples of such devices include end-userdevices—such as computers, peripherals (for example, printers, copiers,storage devices, and scanners), and IP telephones—that includefunctionality for automatically reading information stored in or on thesegment of physical communication media.

In the particular embodiment shown in FIG. 8, the PLI aggregationsoftware 810 comprises software 812 that uses one or more discoveryprotocols to discover and connect with devices that are able to providePLI information to the aggregation point 353 (assuming those devicesalso support those discovery protocols). Examples of discovery protocolsinclude, without limitation, Multicast DNS (mDNS), DNS based ServiceDiscovery (DNS-SD), Universal Plug and Play (UPnP), Simple DeviceDiscovery Protocol (SDDP), and Service Location Protocol (SLP) as wellas proprietary protocols, and extensions of other protocols (such asDynamic Host Configuration Protocol (DHCP)). In this embodiment, when apatch panel 302 (or other device that is able to provide PLI informationto the aggregation point 353) is first coupled to the LAN 352, the MPU330 of the patch panel 302 first obtains an IP address (typically from aDHCP server for the LAN 352). The MPU 330 in the patch panel 302 thenuses the discovery protocol to broadcast an informational message to theother nodes on the LAN 353. The informational message includesinformation about the services that the patch panel 302 provides, whichin this case includes services related to providing PLI information forthe patch panel 302 and patch cords 312 coupled to the patch panels 302.The aggregation point 353 listens for such informational messages. Whenthe aggregation point 353 receives an informational message from a patchpanel 302 that it can manage, the aggregation point 353 uses thediscovery protocols to send a corresponding message to the patch panel302 (using the address information included in the receivedinformational message) requesting more information about the patch panel302. In response to this request, MPU 330 in the patch panel 302provides the requested information. At this point, the aggregation point353 is able to control and receive notifications from the MPU 330 in thepatch panel 302. Similar processing can be performed when other devicesthat provide PLI to an aggregation point 353 (such as the inter-networkdevice) join the LAN 352.

Likewise, when an aggregation point 353 is connected to the LAN 352, thediscovery protocol software 812 uses the discovery protocols tobroadcast an informational message to all the nodes on the LAN 352. Thismessage indicates that the aggregation point 353 is searching fordevices and/or services that include the PLI functionality describedhere. Devices that are able to provide PLI to an aggregation point(devices such as patch panels 320 and inter-network devices) listen forsuch messages. If those devices meet the search criteria set forth inthe message, the devices respond with an appropriate message advertisingthe services they provide. When the aggregation point 353 receives sucha message from a device that it can manage, the software 812 sends amessage to that device (using the address information included in thereceived message) requesting more information about that device. Inresponse to this request, the device provides the requested informationto the aggregation point 353. At this point, the aggregation point 353is able to control and receive notifications from the device.

In this way, when devices that are able to provide PLI to an aggregationpoint are coupled to the LAN 352, the aggregation points 353 is able toautomatically discover the device and start aggregating physical layerinformation for that device without requiring a technician installingthe device to know about the aggregation points that are on the LAN 352.Similarly, when the aggregation point 353 is coupled to the LAN 352, theaggregation point 353 is able to automatically discover and interactwith devices that are capable of providing PLI to the aggregation point353 without requiring the technician installing the aggregation point353 to know about such devices that are on the LAN 352. Thus, thephysical-layer information resources described here can be easilyintegrated into the LAN 352.

In the embodiment shown in FIG. 8, the PLI aggregation software 810 alsoincludes software 814 that is configured to obtain physical layerinformation from the devices it has discovered and connected to usingthe discovery protocol software 812 (for example, devices such as thepatch panels 302 and inter-network devices). A database manager 816 isused to store the PLI information that the aggregation software 810obtains in a database. In the particular embodiment shown in FIG. 8, thesoftware 814 uses one or more appropriate protocols to communicatephysical layer information to and from such devices. Examples ofprotocols that can be used include, without limitation, the FileTransfer Protocol (FTP), the Trivial File Transfer Protocol (TFTP), theHypertext Transfer Protocol (HTTP), the Simple Network ManagementProtocol (SNMP), the Common Gateway Interface (CGI) protocol, theRepresentational State Transfer (REST) protocol, and the Simple ObjectAccess Protocol (SOAP). The devices that the aggregation point 353receives information from also implement at least some of the protocolsimplemented by the aggregation point 353 to organize, track, store, andcommunicate physical layer information.

The aggregation point 353 and aggregation software 810 can also be usedto obtain other types of physical layer information. For example, inthis embodiment, the aggregation software 810 also obtains informationabout physical communication media segments that is not otherwiseautomatically communicated to an aggregation point. One example of suchinformation is information about non-connectorized cables that do nototherwise have information stored in or on them that are attached to apatch panel 302 (including, for example, information indicating whichports of the patch panel 302 are connected to which ports of otherdevices in the network 350 by that cable as well as media informationabout the cable).

Another example of such information is information about patch cordsthat are connected to devices that are not be able to read mediainformation that is stored in or on the patch cords that are attached totheir ports and/or that are not able to communicate such information tothe aggregation point 353 (for example, because such devices do notinclude such functionality, because such devices are used with patchcords that do not have media information stored in or on them, and/orbecause bandwidth is not available for communicating such information tothe aggregation point 353). In this example, this information caninclude, for example, information about the devices themselves (such asthe devices' MAC addresses and IP addresses if assigned to suchdevices), information indicating which ports of the devices areconnected to which ports of other devices in the network, andinformation about the physical media attached to the ports of thedevices. This information can be provided to the aggregation point 353,for example, by manually entering such information into a file (such asa spreadsheet) and then uploading the file to the aggregation point 353in connection with the initial installation of each of the variousitems. Such information can also, for example, be directly entered usinga user interface provided by the aggregation point 353 (for example,using a web browser). In the embodiment shown in FIG. 8, the aggregationpoint software 810 includes a web server 818 to facilitate the upload offiles and/or the direct entry of such manually entered information.

The aggregation software 810 can also obtain information about thelayout of the building or buildings in which the network 350 isdeployed, as well as information indicating where each patch panel 302device, patch cord (or other item of physical communication media), andinter-networking device is located within the building. This informationcan be, for example, manually entered and uploaded to the aggregationpoint 353 in connection with the initial installation of each of thevarious items. In one implementation, such location information includesan X, Y, and Z location for each port or other termination point foreach physical communication media segment that is terminated in thenetwork 350 (for example, X, Y, and Z location information of the typespecified in ANSI/TIA/EIA 606-A Standard—Administration Standard For TheCommercial Telecommunications Infrastructure).

The aggregation software 810 can also obtain and maintain testing, mediaquality, or performance information relating to the various items ofphysical communication media that exist in the network. The testing,media quality, or performance information, for example, can be resultsof testing that is performed when a particular segment of media ismanufactured and/or when testing is performed when a particular segmentof media is installed or otherwise checked.

The aggregation software 810 also provides an interface for externaldevices or entities to access the physical layer information maintainedby the aggregation point 353. This access can include retrievinginformation from the aggregation point 353 as well as supplyinginformation to the aggregation point 353. In this embodiment, theaggregation point 353 is implemented as “middleware” that is able toprovide such external devices and entities with transparent andconvenient access to the PLI maintained by the access point 353. Becausethe aggregation point 353 aggregates PLI from the relevant devices onthe IP network 350 and provides external devices and entities withaccess to such PLI, the external devices and entities do not need toindividually interact with all of the devices in the IP network 350 thatprovide PLI, nor do such devices need to have the capacity to respond torequests from such external devices and entities.

The aggregation point software 810, in the embodiment shown in FIG. 8,implements an application programming interface (API) 820 by whichapplication-layer functionality in such other devices can gain access tothe physical layer information maintained by the aggregation point 353using a software development kit (SDK) that describes and documents theAPI 820. In one implementation of such an embodiment, the API 820 isconfigured to use the Simple Object Access Protocol (SOAP) protocol forcommunications between the aggregation point 353 and such externaldevices or entities. In other implementations, other protocols can beused (for example, the SNMP or CGI protocols).

For example, an application 370 (shown in FIG. 3) executing on acomputer 356 can use the API 820 provided by the aggregation point 353to access the PLI information maintained by the aggregation point 353(for example, to retrieve such information from the aggregation point353 and/or to supply information to the aggregation point 353). Thecomputer 356 is coupled to the LAN 352 and accesses the aggregationpoint 353 over the LAN 352.

FIG. 9 is a block diagram of one embodiment of a network managementsystem (NMS) 380 that is specially configured to use the physical layerinformation that is made available by the system 300 of FIG. 3. Theparticular embodiment of an NMS 380 shown in FIG. 9 is described here asbeing implemented for use in the system 300 of FIG. 3, though otherembodiments can be implemented in other ways.

The NMS 380 is typically implemented as software 900 that executes on aworkstation or other computer 902. The workstation 902 comprises atleast one programmable processor 904 on which the software 900 executes.The software 900 comprises program instructions that are stored (orotherwise embodied) on an appropriate storage medium or media from whichat least a portion of the program instructions are read by theprogrammable processor 904 for execution thereby. The workstation 902also comprises memory 906 for storing the program instructions and anyrelated data during execution of the software 900.

The workstation 902 on which the NMS software 900 executes also includesone or more interfaces 908 that communicatively couple the NMS 380 tothe network elements that the NMS 380 manages and otherwise interactswith. More specifically, the one or more interfaces 908 communicativelycouple the NMS 380 to these network elements over the one or more IPnetworks 350. In one implementation of such an embodiment, at least oneof the interfaces 908 comprises an ETHERNET network interface forcoupling the NMS 380 to the one or more IP networks 350.

The NMS software 900 comprises network management functionality 910 thatimplements various conventional NMS functions, such as displaying statusand alarm information about the various elements in the managed network.In the particular embodiment described here, the NMS functionality 910includes functionality for displaying a user interface for the NMS 380and data management functionality for organizing, tracking and storingthe information it receives from the managed network elements.

The NMS software 900 also includes physical layer information (PLI)functionality 914. The PLI functionality 914 is configured to retrievephysical layer information from the aggregation point 353 and provide itto the NMS functionality 910 for use thereby. The NMS functionality 910uses the retrieved physical layer information to perform one or morenetwork management functions. In the embodiment shown in FIG. 9, the PLIfunctionality 914 retrieves physical layer information from theaggregation point 353 using the API 820 (shown in FIG. 8) implemented bythe aggregation point 353. To do this, the PLI functionality 914supports the protocol used by the API 820. The NMS software 900communicates with the aggregation point 353 over the IP networks 350.The aggregation point software 800 executing on the aggregation point353 processes and responds to API calls from the NMS 380.

The retrieved physical layer information can be used by the NMS 380 toprovide Layer 1 (of the OSI model) resolution in the information itdisplays. For example, in one implementation of the embodiment shown inFIG. 9, the NMS software 900 displays a graphical representation of themanaged network that shows the logical communication links betweenvarious network elements. When a user clicks on one of the logicalcommunication links, the NMS software 900 uses the PLI functionality 914to display the various physical layer items (for example, physicalcommunication media, patch panels, and wall outlets) that implement thatlogical communication link, as well as information about those physicallayer items (for example, their location, product name, type, color,length, temperature, etc.) that was retrieved from the aggregation point353.

In the particular embodiment shown in FIG. 9, the NMS software 900 alsoincludes physical layer management functionality 912 that uses thephysical layer information received from the aggregation point 353 tocarry out various PLM functions. For example, the PLM functionality 912enables the NMS 380 to manage patch cord moves, adds, or changes (MAC)for the patch panels 302. This can be done by having the PLMfunctionality 912 communicate information about the MAC to a computer orother device used by the technician using the network 350. Thisinformation can include physical layer information received from anaggregation point 353 (for example, information identifying particularports 304, patch panels 302, and patch cords 312 involved in the MAC andthe locations thereof as well as information about the visual attributesof the items involved in the MAC). Also, the PLM functionality 912enables the NMS 380 to receive alarms and warning messages from theaggregation point 353 that are related to moves, adds, or changes (forexample, when an unrequested move, add, or change has been made or wherea requested move, add, or change was made incorrectly). In other words,the PLM functionality 912 in the NMS 380 can be used to verify that aparticular requested MAC was properly implemented and, if it was not,inform the technician of that fact. In addition, the PLM functionality912 in the NMS 380 can be configured to perform a “guided” MAC in whichthe PLM functionality 912 causes appropriate LEDS 316 on the patchpanels 302 to be illuminated or flashed in order to help the technicianidentify the ports 304 involved in a MAC. The PLM functionality 912 cando this by using an appropriate API call to request that the LEDs 316 beilluminated. The aggregation point 353, in response to such an API call,sends a request to the appropriate MPU 330 to have the appropriate slaveprocessor modules 318 cause the LEDs 316 to be illuminated.

This MAC functionality can be implemented as a standalone applicationthat is not a part of a NMS 380.

Other examples of functions that the NMS 380 can perform using thephysical layer information include raising an alarm or warning if apredetermined specific patch cord (or a particular type of patch cord)is not used to implement a particular cross connection, enforcing otherpolicies, and/or using the location information included in the physicallayer information to assist in E911 or location based services (LBS)processing that the NMS 380 supports (for example, to determine where anIP phone is located).

Another example of PLI-enabled functionality that can be added to an NMS380 is shown in FIG. 10. FIG. 10 is a flow diagram of one exemplaryembodiment of a method of compliance tracking in a network that includesthe PLI functionality described here. The particular exemplaryembodiment of method 1000 shown in FIG. 10 is described here as beingimplemented as a part of the PLI functionality 914 of the NMS 380 shownin FIG. 9 for use in the system 300 shown in FIG. 3 (though otherembodiments can be implemented in other ways).

In such an exemplary embodiment, the physical layer information that istracked and aggregated at the aggregation point 353 includes informationabout the compliance of various parts of the system 300 with variousstandards. Standards such as the TIA/EIA-568-B family of standardsdefine performance requirements for various physical layer cablingcomponents that are used to implement networks, performance requirementsfor “permanent links” included within a give channel, and performancerequirements for the overall channel.

For each channel that is being installed, information about thecompliance of each patch cord 312 and plug 314 used in the channel withthe requirements of the relevant standards is stored in the relevantnon-volatile memory 392 (block 1002). This information can be determinedby tests performed by the manufacture and/or an installer. Thisinformation can include an indication of whether or not each componentassociated with that patch cord 312 complies with the relevantperformance specifications as well as the underlying performanceinformation that was used to determine compliance. In other words, theperformance margin or envelope for each such component can be stored inthe relevant EEPROM 392. This component compliance data is automaticallyread when the patch cord 312 is connected to a port 304 of the patchpanel 302 and communicated to the relevant aggregation point 352 (block1004).

When a particular permanent link is installed (for example, a linkbetween a wall outlet and a punch down block of a patch panel 302), theinstaller tests the performance of the permanent link and certifies itscompliance with the requirements of the relevant standards (block 1006).Information about the compliance of the permanent link with therequirements of the relevant standards is communicated to theaggregation point 353 (for example, by uploading such information asdescribed above) (block 1008). This information can include anindication of whether or not the permanent link complies with therelevant performance requirements as well as the underlying performanceinformation that was used to determine compliance. In other words, theperformance margin or envelope for the permanent link can be provided tothe aggregation point 353 in addition to an indication of compliance.

In the embodiment shown in FIG. 10, the installer also tests the overallchannel and certifies the compliance of the overall channel with therequirements of the relevant standards (block 1010). Information relatedto the compliance of the overall channel is communicated to theaggregation point 353 (for example, by uploading such information asdescribed above). The aggregation point 353 then identifies theparticular components that were used in the channel when the channel wascertified (block 1012). For example, the aggregation point 353 knowswhich patch cords 312 and patch panel ports 304 were used in the channelwhen it was certified. If in the future one of those patch cords 312were to be replaced, the aggregation point 353 is able to automaticallydetermine that the original basis for the certification of channelcompliance no longer exists (block 1014). When such a patch cord 312 isreplaced, the aggregation point 353 can also automatically determine ifthe overall channel likely remains compliant with the relevant standardsby checking if the replacement path cord has been certified to meet thecomponent specifications needed for channel compliance and verifyingthat the permalink link for the channel remains undisturbed and that thepatch cord is connected to the same ports as before (block 1016). Suchinformation can be used in troubleshooting performance problems in thenetwork.

Method 1000 is one example of how such compliance information can beused. Also, the embodiment of method 1000 shown in FIG. 10 is describedhere as being implemented in the NMS 380 of FIG. 8, though it is to beunderstood that similar functionality can be implemented in other partsof the system 300 (for example, in the aggregation point 353 or as astandalone application). Moreover, other types of compliance informationcan be received and stored by an aggregation point and used incompliance tracking Examples of such compliance information include,without limitation, information about compliance with communications,regulatory, or military rules, regulations, laws, specifications, orstandards.

FIG. 11 is a block diagram of one embodiment of an inter-networkingdevice 354 that is specially configured to use the physical layerinformation that is made available by the system 300 of FIG. 3. Theparticular embodiment of an inter-networking device 354 shown in FIG. 11is described here as being implemented for use in the system 300 of FIG.3, though other embodiments can be implemented in other ways.

In the embodiment shown in FIG. 11, the inter-networking device 354comprises at least one programmable processor 1100 that executessoftware 1102 (referred to as “firmware” in some embodiments) thatcauses the inter-networking device 354 to carry out various functionsdescribed below. The software 1102 comprises program instructions thatare stored (or otherwise embodied) on an appropriate storage medium ormedia (for example, flash memory) from which at least a portion of theprogram instructions are read by the programmable processor 1100 forexecution thereby. The inter-networking device 354 also includes memory1104 that is coupled to the programmable processor 1100 for storingprogram instructions and data.

The inter-networking device 354 includes a plurality of ports 1106. Eachport 1106 includes a suitable interface for coupling physicalcommunication media to the inter-networking device 1106. Each suchinterface includes, for example, a mechanical structure for attachingthe physical communication media to the inter-networking device 354 anda physical layer device (PHY) to send and receive signals over theattached communication media. In one such embodiment, the ports 1106 areETHERNET ports.

The software 1102 comprises inter-networking functionality 1108 thatcauses the inter-networking device 354 to perform one or moreinter-networking functions for which it was designed. Examples ofinter-networking functions include Layer 1, Layer 2, and Layer 3 (of theOSI model) inter-networking functions such as the routing, switching,repeating, bridging, and grooming of communication traffic that isreceived at the inter-networking device 354 via the plurality of ports1106.

The software 1102 also comprises management functionality 1110 thatenables the inter-networking device 354 to be configured and managed. Inthe particular embodiment shown in FIG. 11, the management functionality1110 includes a web server (and related web content and applications)that enables a user to directly interact with the inter-networkingdevice 354 using a web browser. In this embodiment, the managementfunctionality 1110 also includes SNMP functionality for interacting withan NMS (such as NMS 380) using the SNMP protocol. SNMP commands andresponses are communicated over the one or more IP networks 350 via oneor more of the ports 1106 of the inter-networking device 354.

The software 1102 also includes physical layer information (PLI)functionality 1112. The PLI functionality 1112 is configured to retrievephysical layer information from the aggregation point 353 and provide itto the inter-networking functionality 1108. The inter-networkingfunctionality 1108 uses the retrieved physical layer information toperform one or more inter-networking functions. In the embodiment shownin FIG. 11, the PLI functionality 1112 retrieves physical layerinformation from the aggregation point 353 using the API 820 (shown inFIG. 8) implemented by the aggregation point 353. To do this, the PLIfunctionality 1112 supports the protocol used by the API 820. Thesoftware 1102 in the inter-networking device 354 communicates with theaggregation point 353 over the IP networks 350. The aggregation pointsoftware 800 executing on the aggregation point 353 processes andresponds to API calls from the inter-networking device 354. Theinter-networking device 354 can also retrieve at least some of thephysical layer information from an NMS or other network element.

Some communication protocols (for example, the IEEE 802.3 family ofETHERNET standards) include functionality for automatically determininga suitable communication rate for a given communication link (forexample, the IEEE 802.3 auto-negotiation, auto-sensing, andauto-fallback features). This type of functionality performs tests tomake such determinations. In other words, the physical communicationmedia is still, from the perspective of such an inter-networking device,a “black box.” The physical layer information provided to theinter-networking functionality 1108 by the PLI functionality 1112enables the inter-networking functionality 1108 to treat the physicallayer as a “white box” for which it has accurate information to use incarrying out its inter-networking functions (for example, to use inmaking bridging, routing, or switching decisions). In one implementationof such an embodiment, the physical layer information received from theaggregation point 353 is provided to the inter-networking functionality1108 to assist it in performing such auto-rate selection procedures.

Moreover, where such conventional rate-determination functionality isused in making inter-networking decisions (such as, decisions as towhich port to route data on), such conventional functionality istypically only able to characterize communication links that aredirectly connected to the inter-networking device. This means that ifthere is a segment of physical communication media that is one or more“hops” away from the inter-networking device that is of a lower quality(for example, because it supports lower communication rates) than thephysical communication media used to implement the link that is directlyattached to the inter-networking device, the inter-networking devicewould be unaware of that fact and would not take that fact into accountin make routing or other inter-networking policy decisions. In theembodiment shown in FIG. 11, the physical layer information receivedfrom the aggregation point 353 (and from other sources such as the NMS380) can be used to identify such situations and respond accordingly.

The physical layer information received from the aggregation point 353can be used in other ways. For example, the inter-networkingfunctionality 1108 can be configured to constrain the routing ofcommunication traffic by a policy that dictates that traffic received onsome ports 1106 can only be communicated through certain areas of abuilding or buildings (for example, only through “secure” areas of thebuilding). In order for such a policy to be enforced, theinter-networking functionality 1108 needs to know where traffic that isoutput on each of its ports 1106 will pass. The physical layerinformation received from the aggregation point 353 can be used to makesuch determinations.

In another example, the inter-networking functionality 1108 isconfigured to enforce a policy that requires only certain types ofphysical communication media to be use with it (for example, requiringthe use of certain brands or types or lengths of patch cords). Thephysical layer information received from the aggregation point 353 canbe used by the inter-networking functionality 1108 to enforce such apolicy (for example, by not forwarding data received on ports 1106 thathave non-compliant media connected to them and/or by raising alarms orwarnings when non-compliant media is connected to a port 1106). In otherwords, the inter-networking functionality 1108 can be configured to actas a “bus guardian” that enforces a “virtual keying” scheme in which atleast some of the media information stored in or on a patch cord 312 isused to “key” the patch cord 312.

As noted above in connection with FIG. 1, inter-networking devices canalso include media reading interfaces to read media information that isstored in or on the segments of physical media that are attached to itsports and to communicate the media information it reads from theattached segments of media (as well as information about theinter-networking device itself) to an aggregation point. For example, asshown in FIG. 11, each port 1106 has an associated media readinginterface 1120 that the programmable processor 1100 uses to read mediainformation that is stored in or on the segments of physical media thatare attached to its ports 1106. The programmable processor 1100 in thisexample communicates the media information that it has read to asuitable aggregation point using one or more of the communication linksthat are established via one of its ports 1106.

In other implementations, the inter-networking device 354 does notinclude media reading interfaces, and the physical layer informationrelated to the physical media attached to its ports is provided to anaggregation point in other ways (for example, by manually entering anduploading the information).

FIG. 12 illustrates another example of how physical layer informationthat is captured and aggregated using the techniques described here canbe used to improve the efficiency of the inter-networking devices usedin a network. In the example shown in FIG. 12, the network 1200 isimplemented as a mesh network of Layer 2 devices 1202 (typicallyETHERNET switches) that bridge various ETHERNET LAN segments 1204together. In such an ETHERNET network 1200, a minimum spanning tree isconstructed and those links that are not part of the spanning tree aredisabled by disabling the corresponding ports of the switches 1202. As aresult, a single active path exists between any two nodes in the network1200. One or more redundant links can also be defined to provide backuppaths that can be used if a link in the active path fails. The spanningtree is constructed in order to avoid loops.

In conventional ETHERNET networks, a spanning tree protocol thatcomplies with the IEEE 802.1D MAC Bridges standard is used to constructa spanning tree for the network. However, the spanning tree algorithmused in conventional ETHERNET networks is a “distributed” algorithm, inwhich the relevant switch must learn what devices are connected to it,exchange messages with the other switches, take part in electing a rootbridge, and maintain a forwarding database. Also, when a new switch isadded to the network, all the switches in the network must be informedby the root bridge of any topology changes that result from adding thenew switch, in which case the other bridge devices must update theforwarding databases they maintain.

Because a distributed spanning tree protocol is used in conventionalETHERNET networks, each switch must include sufficient processing powerto implement the spanning tree protocol and to perform database look-upswhen making decisions regarding how to forward packets it receives. Inaddition, changes to the spanning tree topology can take a significantamount of time to propagate through the network, which may lead todegraded network performance or, in some cases, loops. Also, the degreeto which a conventional switch can learn about the network is limited,which can also lead to degraded network performance.

Moreover, each such conventional switch typically uses transparentbridging to forward packets using the forwarding database. Theforwarding database is initially empty and entries are added to thedatabase as the switch receives packets. When a switch receives apacket, it inspects the source MAC address of the packet and adds anentry to the forwarding database for that source MAC address (if onedoes not already exist) that associates that MAC address with the porton which the packet was received. The switch also inspects thedestination MAC address of the packet and searches for an entry in theforwarding database for that destination MAC address. If an entry is notfound in the forwarding database for that destination MAC address, thepacket is flooded to all other ports of the switch. In the future, whenthe switch receives a packet from the device that has that MAC addressas its source MAC address, the switch adds an entry to its forwardingdatabase that associates that MAC address with the port on which thepacket was received. In this way, the switch is able to build up aforwarding database over time. The forwarding database needs to beupdated as the topology of the network changes (for example, due to apatch cord being moved or removed, failure of links, the addition ordeletion of a switch, or the movement of an end-user device).

Because the forwarding database is maintained separately in each switchin a conventional ETHERNET network, each such switch must havesufficient processing power to perform such processing. Also, when thenetwork topology changes occur, the performance of the network can bedegraded, as the switches flood the network in order to learn the newtopology of the network.

In the example shown in FIG. 12, centralized bridge functionality 1206is deployed in the network 1200 to alleviate some of the problems notedabove. The centralized bridge functionality 1206 interacts with the oneor more aggregation points 1208 that aggregate physical layerinformation for the network 1200. In the particular example shown inFIG. 12, the central bridge functionality 1206 is deployed in an NMS1210. The aggregation point 1208 collects the MAC addresses of the enddevices 1212 that are on the network 1200 as well as information aboutthe switches 1202.

In the example shown in FIG. 12, for some of the end devices 1212, mediainformation for each segment of physical media that connects each suchend device 1212 to a switch 1202 is automatically read and communicatedto an aggregation point 1208. That is, the end devices 1212 include anappropriate media reading interfaces and driver software to read mediainformation that is stored on an ETHERNET cable connected to that enddevice 1212 and provide the media information for the ETHERNET cable, aswell the MAC address for the end device 1212 and its current IP address,to an aggregation point 1208. If the end device 1212 is connected to aswitch 1202 via one or more intermediary devices (such as a wall outletand one or more patch panels), each such intermediary device wouldinclude appropriate media reading interface functionality to read themedia information and provide to the aggregation point 1208. In thisway, the aggregation point 1208 would be able to associate the MACaddress of each such end device 1212 with a port of the switch 1202.

Also, in the example shown in FIG. 12, for some of the end devices 1212,media information for at least one segment of physical communicationmedia that connects each such end device 1212 to a switch 1202 is notautomatically read and communicated to an aggregation point 1208. Forthese end devices 1212, physical layer information for each segment ofphysical communication media that connects the end devices 1212 to portsof the switch 1202 and the MAC addresses for the end devices 1212 can bemanually entered and uploaded to the aggregation point 1208 (asdescribed above). Alternatively, the central bridge functionality 1206and/or the aggregations point 1208 can obtain such information in otherways. For example, the associations between the MAC addresses of the enddevices 1212 and the ports of the switch 1202 can be learned from theNMS 1210.

The central bridge functionality 1206 uses the physical layerinformation and MAC address information it has received to associate theMAC address for each end device 1212 with the port of the particularswitch 1202 to which the end device 1212 is connected. Then, the centralbridge functionality 1206 determines a minimum spanning tree for thenetwork 1200 using that information and determines a corresponding STPstate (typically, “blocking”, “forwarding”, or “disabled”) for each portof each switch 1202. The central bridge functionality 1206 thendetermines how the forwarding database for each of the switches 1202should be configured based on the spanning tree and the MAC addressinformation the central bridge functionality 1206 has. The port stateinformation and forwarding database information is then communicated toeach of the switches 1202.

Each of the switches 1202 includes corresponding bridge functionality1214 to receive the port state information and forwarding databaseinformation from the central bridge functionality 1206. The bridgefunctionality 1214 in each switch 1202 configures the switch 1202 sothat each port is in the particular STP state specified by the centralbridge functionality 1206 for it. Also, the bridge functionality 1214 ineach switch 1202 uses the forwarding database information it receivesfrom the central bridge functionality 1206 to configure its forwardingdatabase 1216.

When changes occur to the network 1200, the aggregation point 1208(and/or the other source of MAC address information such as the NMS1210) will see the changes and provide updated information to thecentral bridge functionality 1206. The central bridge functionality 1206can modify the spanning tree topology, if needed, and determine what (ifany) changes to each switch's port states and forwarding databases 1216need to be made in response to the changes in the network 1200.

By having the central bridge functionality 1206 determine the spanningtree for the network 1200 and configure the forwarding databases 1216 inthe switches 1202, the switches 1202 need not perform such processingand, instead, the resources in the switch 1202 can be dedicated toforwarding packets. Also, the central bridge functionality 1206 is ableto directly learn of changes in the network 1200 from the aggregationpoint 1208 and quickly respond to such changes and communicate anyneeded changes to the switches 1202. All of this should improve theperformance of the network 1200. Moreover, the central bridgefunctionality 1206, because it has access to more information about thenetwork 1200, can more effectively create the spanning tree (forexample, by assembling the spanning tree based on the type, number,location, length, etc. of physical communication media used to implementthe various logical communication links in the network 1200).

FIG. 13 illustrates an alternative embodiment of a system 300′ thatincludes physical layer information functionality as well as physicallayer management functionality. The system 300′ is similar to the system300 of FIG. 3 except as described below. Those elements of the system300′ that are same as the corresponding elements of system 300 arereferenced in FIG. 13 using the same reference numerals, and thedescription of such elements is not repeated below in connection FIG.13.

The main difference between the system 300 of FIG. 3 and the system 300′of FIG. 13 is that, in the system 300′ of FIG. 13, the master processorunit and slave processor unit are combined together into a singlecombined master/slave processor unit 330/318 that is included in eachpatch panel 302′. That is, each patch panel 302′ includes the masterprocessor unit 330 unit functionality shown in FIG. 6 (for example, eachpatent panel 302′ includes master processor 332 and ETHERNET interface340). Also, each patch panel 302′ directly communicates with anappropriate aggregation point 353. As a result, a backplane is notneeded to communicate between the master processor unit functionalityand the slave processor unit functionality.

FIGS. 14-16 illustrate yet another alternative embodiment of a system300″ that includes physical layer information functionality as well asphysical layer management functionality. The system 300″ is similar tothe system 300 of FIG. 3 except as described below. Those elements ofthe system 300″ that are same as the corresponding elements of system300 are referenced in FIGS. 14-16 using the same reference numerals, andthe description of such elements is not repeated below in connectionFIGS. 14-16.

The main difference between the system 300 of FIG. 3 and the system 300″of FIGS. 14-16 is that the patch panels 302″ and the MPU 330″communicate over a main bus 328 using protocols specified in theInstitute of Electrical and Electronics Engineers (IEEE) 802.14.5standard. Although the IEEE 802.14.5 protocols are typically used forwireless communications, in the embodiment shown in FIGS. 14-16, thepatch panels 302″ and MPU 330″ use the IEEE 802.14.5 protocols tocommunicate over one or more CATV coaxial cables.

In such an embodiment, the main bus 328 is physically implemented usingone or more coaxial cables, where the data communications arecommunicated along the coaxial cables in a suitable radio frequency bandand where the MPU 330″ supplies DC power over the coaxial cables for useby the active components of each patch panel 302″. The slave processormodule 318″ in each patch panel 302″ includes a suitable bus interface326 (shown in FIG. 15) to couple the slave processor 320 to the masterprocessor module 330″, and the master processor unit 330″ includes asuitable bus interface 338 (shown in FIG. 16).

In such an embodiment, the patch panel software 322 and the main businterfaces 326 of each patch panel” 302 and the MPU software 334 and themain bus interface 338 of the MPU 330″ comprises suitable functionalityto enable the programmable processor 320 in each patch panel 302″ andthe programmable processor 332 in the MPU 330″ to send and receive datausing the IEEE 802.14.5 protocol as well as connectors (such as “F”connectors) to connect each patch panel 302″ and the MPU 330″ to thecoaxial cables used to implement the main bus 328 (via for example, atap or splitter). The addressing scheme of the IEEE 802.14.5 protocolssupports up to 127 patch panels (each patch panel 302′ supporting up to48 ports, for a total of 6096 ports) and one MPU 330″. The IEEE 802.14.5protocols are designed for low-power applications, which is especiallywell-suited for use in the embodiment shown in FIGS. 14-16.

Also, in the embodiment shown in FIG. 14-16, power is supplied to eachpatch panel 302″ (more specifically, to the active components of eachpatch panel 302″) over the main bus 328. The PSU 344 in the MPU 330″converts the external power received from the external power source 346to power that is suitable for use by the components of the MPU 330″ andfor supply to the patch panels 302″.

FIG. 17 is a block diagram of one embodiment of a wall outlet 1700 thatincludes functionality to obtain physical layer information. Theembodiment of a wall outlet 1700 shown in FIG. 17 is described here asbeing implemented for use with the system 100 of FIG. 1, though otherembodiments can be implemented in other ways.

The wall outlet 1700 is configured to be installed in or on a wall orsimilar structure. The wall outlet 1700 includes a set of ports 1702similar to the ports described above in connection with FIGS. 1-16. Theports 1702 are also referred to here as “downstream” ports 1702. Ingeneral, each downstream port 1702 includes a respective front connector(or other attachment point) in which a connectorized cable (or othersegment of physical media) can be attached. An example of such aconnectorized cable is a twisted-pair cable having RJ-45 plugs at eachend. Each downstream port 1702 also includes a rear attachment pointthat is connected to a corresponding port of a switch 1708. The switch1708 is used to communicatively couple each of the downstream ports 1702to a patch panel (not shown in FIG. 17) over a single cable, which isattached to the wall outlet 1700 via an upstream port 1712. In oneimplementation of such an embodiment, the upstream port 1712 isconfigured to be used with a non-connectorized cable. This cable istypically routed through a building (for example, over, under, around,and/or through walls, ceilings, floors, and the like) and is typicallynot easily or frequently moved.

The switch 1708 includes a switching function 1710 that switches datapackets among the downstream ports 1702 and the upstream port 1712. Theswitching function 1710 is implemented, for example, in software,hardware, or combinations thereof.

The downstream ports 1702 of the wall outlet 1700 are configured to beused with connectorized cables that have media information stored in oron them (for example, as described above in connection with FIGS. 1-16).The wall outlet 1700 includes a media reading interface 1704 for eachdownstream port 1702. In this embodiment, the media read interfaces 1704are implemented in the same manner as the media reading interfacesdescribed above in connection with FIGS. 1-16. Each media readinginterface 1704 is used to read the media information stored in or on theconnectorized cable that is inserted into the corresponding downstreamport 1702. The media information that is read from the connectorizedcables that are inserted into the downstream ports 1702 is communicatedfrom the media reading interfaces 1704 to a programmable processor 1706.In the embodiment shown in FIG. 17, the programmable processor 1706 is apart of the switch 1708.

The programmable processor 1706 executes software that is similar to thesoftware that is executed by the programmable processors described abovein connection with FIGS. 1-16 (including, for example, a web server orother software that enables a user to interact with the processor 1706).The main difference is that the programmable processor 1706, in theembodiment shown in FIG. 17, communicates with a suitable aggregationpoint using the logical communication link that is provided using theupstream port 1712. The wall outlet 1700 can be used to capture, andcommunicate to a suitable aggregation point, physical layer informationrelated to the wall outlet 1700 itself, the connectorized cablesinserted into the downstream ports 1702, and the non-connectorized cableattached to the upstream port 1712.

As noted above, the techniques described here for reading mediainformation stored in or on a segment of physical communication mediacan be used in one or more end nodes of the network. For example,computers (such as, laptops, servers, desktop computers, orspecial-purpose computing devices such as IP telephones, IP multi-mediaappliances, and storage devices) can be configured to read mediainformation that is stored in or on the segments of physicalcommunication media that are attached to its ports and to communicatethe media information it reads from the attached segments of media (aswell as information about the device itself) to an aggregation point.FIG. 18 is one embodiment of such a computer 1800. The computer 1800includes a network interface card (NIC) 1802 that is used to connect thecomputer 1800 to an IP network (for example, an ETHERNET local areanetwork). The NIC 1802 includes a port 1804 that is used to physicallyattach a suitable cable (for example, a CAT-5/6/7 cable) to the NIC1802. The NIC 1804 also includes standard NIC functionality 1806 forcommunicating over the IP network (for example, a suitable physicallayer device (PHY) and media access control (MAC) device). The NIC 1802enables one or more processors 1808 (and the software 1810 executingthereon) included in the computer 1800 to communicate with the IPnetwork. In this embodiment, the NIC 1802 includes a media readinginterface 1812 that the one or more processors 1808 use to read mediainformation stored on or in the cable that is attached to the computer1800. The media information that is read from the cable, as well asinformation about the NIC 1802 and the computer 1800 (for example, anyassigned MAC address or IP addresses) can be communicated to a suitableaggregation point as described above. In one implementation of such anembodiment, a NIC software driver 1814 used with the NIC 1802 includesphysical layer information (PLI) functionality 1816 that causes theprocessor 1808 to read and communicate such physical layer information.The NIC 1802 and MRI 1812 are coupled to the processor 1808 using asuitable bus or other interconnect (not shown). In this way, informationabout the computer 1800 can be automatically obtained and used in thevarious applications described.

Functionality for reading media information stored in or on physicalcommunication media can be integrated into one or more of the integratedcircuits (or other circuits or devices) that communicate over thecommunication media. For example, functionality for reading such mediainformation can be integrated into an ETHERNET physical layer deviceused in a switch. One such example is shown in FIG. 19.

FIG. 19 is a block diagram of one exemplary embodiment of an ETHERNETswitch 1900 that uses a physical layer device (PHY) 1902 that includesintegrated functionality for reading media information. In theparticular exemplary embodiment shown in FIG. 19, the PHY 1902 is in anoctal ETHERNET PHY that includes ETHERNET physical layer functionalityfor eight ETHERNET ports (though it is to be understood that thetechniques described here in connection with FIG. 19 can be used withphysical layer devices having a different number of ports). In thisembodiment, eight RJ-45 jacks 1904 are coupled to the PHY 1902. Each ofthe RJ-45 jacks 1904 is configured to receive an RJ-45 plug attached toa CAT-5, 6, or 7 twisted-pair cable. For each RJ-45 jack 1904, thetransmit conductors (TX+ and TX−) and receive conductors (RX+ and RX−)of that RJ-45 jack 1904 are coupled to transmit pins (TX+ and TX−) andreceive pins (RX+ and RX−), respectively, of the PHY 1902 usingappropriate isolation transformers (not shown) that are eitherintegrated into the jack 1904 itself or that are external to it.

The PHY 1902 includes the required ETHERNET physical sublayers—includinga Physical Medium Dependent (PMD) sublayer 1908 (which includes anappropriate transceiver for the physical communication media that areused with the switch 1900), a Physical Medium Attachment (PMA) sublayer1910 (which performs PMA framing, octet synchronization/detection, andscrambling/descrambling), and a Physical Coding Sublayer (PCS) 1912(which performs auto-negotiation and encoding/decoding). The PHY 1902also includes an appropriate Medium Independent Interface (MII) 1914(for example, a Medium Independent Interface, a Reduced MediaIndependent Interface (RMII), a Gigabit Media Independent Interface(GMII), and/or a Serial Media Independent Interface (SMII)) to connectthe PHY 1902 to an ETHERNET media access control (MAC) device 1916. Asnoted above, in the particular exemplary embodiment shown in FIG. 19,the PHY 1902 is designed for use in an ETHERNET switch 1900 and, as aresult, the MAC 1916 is a switch MAC device that includes appropriatefunctionality to implement an ETHERNET switch.

The PHY 1902 typically also includes other standard ETHERNET physicallayer functionality. For example, the PHY 1902 includes managementfunctionality 1920 for controlling and managing the PHY 1902 and amanagement data input/output (MDIO) interface for communicatingmanagement information between the PHY 1902 and the MAC 1916. Otherstandard ETHERNT physical functionality includes, Medium DependentInterface Cross-Over (MDIX) functionality and clock functionality (bothof which are not shown in FIG. 19).

In the exemplary embodiment shown in FIG. 19, each RJ-45 jack 1904includes a media reading interface 1906 that can be used to determine ifan RJ-45 plug is inserted into that RJ-45 jack 1904 and, if one is, toread the media information stored in an EEPROM attached to the RJ-45plug (if there is one). Example configurations of such a media interface1906 and a suitable RJ-45 plug are described above and in the '395application, the '208 application, and the '964 application.

In this embodiment, a four line media reading interface 1906 is used.One line is used for communicating data (using a serial data protocol),one line is used for power, and one line is used for ground. In thisparticular embodiment, a fourth line is also provided for potentialfuture possible uses or upgrades.

The PHY 1902 includes appropriate pins (or other inputs) for connectingto each of the eight media reading interfaces 1906. The PHY 1902 alsoincludes physical layer information (PLI) functionality 1918 that iscoupled to the eight media reading interfaces 1906.

In the particular exemplary embodiment shown in FIG. 19, the PLIfunctionality 1918 is configured to provide the power and ground signalson the power and ground lines of each of the media reading interfaces1906. For example, the PLI functionality 1918, in one implementation, isconnected to the main power input of the PHY 1902 in order to provide asuitable power signal on the power lines of each of the media readinginterfaces 1906. Also, the PLI functionality 1918 is connected to themain ground input of the PHY 1902 in order to provide a connection toground for each of the ground lines of the media reading interfaces1906.

In the particular exemplary embodiment shown in FIG. 19, the PLIfunctionality 1918 is configured to monitor the eight media readinginterfaces 1906 and determine when an RJ-45 plug has been inserted intoeach of the RJ-45 jacks 1904. This can be done using the schemesdescribed in the '395 application, the '208 application, and the '964application. The PHY device 1902 includes one or more registers 1922(also referred to here as “PLI registers” 1922) in which the PLIfunctionality 1918 stores PLI-related information. One byte of the PLIregister 1922 (also referred to here as the “state byte”) is used tostore information about the state of each of the eight jacks 1904, whereeach bit of the state byte represents the state of a respective one ofthe jacks 1904. When the state of a particular jack 1904 changes (thatis, when a plug is inserted into a previously empty jack 1904 or a plugis removed from a jack 1904), the PLI functionality 1918 is able todetect such change and change the state of the corresponding bit in thestate byte stored the PLI registers 1922.

The PLI functionality 1918 in the PHY device 1902 is also configured to,when instructed to do so, read the media information stored in an EEPROM(if there is one) attached to an RJ-45 plug that is inserted into a jack1904. Data that is read from the EEPROM is stored in the PLI registers1922 of the PHY device 1902. Also, the PLI functionality 1918 isconfigured to, when instructed to do so, write data stored in the PLIregisters 1922 to an EEPROM attached to an RJ-45 plug that is insertedinto a jack 1904.

In the particular exemplary embodiment shown in FIG. 19, a hostprocessor 1930 is coupled to the MAC device 1916 via an appropriate hostinterface. The host processor 1930 executes software 1932 (also referredto here as the “host software”). The host software 1932 comprisesprogram instructions that are stored (or otherwise embodied) on anappropriate storage medium or media from which at least a portion of theprogram instructions are read by the host processor 1930 for executionthereby.

In this exemplary embodiment, the host processor 1930 includes a TCP/IPstack 1934 and management software 1936 that implements variousmanagement and configuration related functionality (for example, aSimple Network Management Protocol (SNMP) agent and a web and/or TELNETserver by which a user can interact with the management software 1936running on the switch 1900).

In the exemplary embodiment shown in FIG. 19, the host software 1932also includes PLI software 1938 that is configured to communicatephysical layer information associated with the switch 1900 and thecables connected to it to an aggregation point over the network to whichthe switch 1900 is connected. In one implementation of the switch 1900,the PLI software 1938 implements the protocols described above toparticipate in the discovery processing supported by the aggregationpoint and to send PLI to the aggregation point. Also, in otherimplementations, the PLI software 1938 interacts with an aggregationpoint solely using the API (or other external interface technology) thatthe aggregation point provides for application-layer functionality tointeract with it. In yet other implementations, the PLI software 1938interacts with the aggregation point via a NMS or other intermediarydevice or system (for example, using a protocol supported by the NMSsuch as SNMP).

The PLI software 1938 executing on the host processor 1930 periodicallyreads the state byte stored in the PLI registers 1922 in the PHY 1902 byinstructing the MAC device 1916 (via the host interface between the hostprocessor 1930 and the MAC device 1916) to read the contents of thestate byte (via the MDIO interface between the MAC device 1916 and thePHY device 1902).

When an RJ-45 plug is inserted into a jack 1904, the PLI software 1938executing on the host processor 1930 will learn of that fact when itreads the state byte stored in the PLI registers 1922 of the PHY device1902. Then, the PLI software 1938 causes (via the host interface betweenthe host processor 1930 and the MAC device 1916) the MAC device 1916 toinstruct (via the MDIO interface between the MAC device 1916 and the PHYdevice 1902) the PLI functionality 1918 in the PHY device 1902 to readthe media information stored in the EEPROM (if any) attached to thenewly inserted RJ-45 plug. The PLI functionality 1918 in the PHY device1902 stores the media information it reads from the EEPROM in the PLIregisters 1922. Once this is complete, the PLI software 1938 can obtainthat media information by causing (via the host interface between thehost processor 1930 and the MAC device 1916) the MAC device 1916 to read(via the MDIO interface between the MAC device 1916 and the PHY device1902) the corresponding PLI registers 1922 in the PHY device 1902. Themedia information read by the MAC device 1916 is then provided to thePLI software 1938 via the host interface. The PLI software 1938 can thencommunicate that information to an aggregation point as described above.

In addition to communicating PLI about the switch 1900 and any cablesconnected to the jacks 1904 of the switch 1900, the switch 1900 can alsoimplement one or more of the inter-networking features described abovein connection with FIGS. 11-12.

Another example of an ETHERNET physical layer device having integratedfunctionality for reading media information stored in or on physicalcommunication media is shown in FIG. 20. FIG. 20 is a block diagram ofone exemplary embodiment of a computer 2000 that uses a physical layerdevice (PHY) 2002 that includes integrated functionality for readingmedia information. The functionality for reading media informationstored in or on CAT 5, 6, or 7 cables is integrated into the PHY 2002 inthe same manner as described above in connection with FIG. 19.Accordingly, elements of the computer 2000 that are substantiallysimilar to corresponding elements described above in connection withFIG. 19 are referenced in FIG. 20 using the same text labels as used inFIG. 19 and reference numerals with the same last two digits as thoseused in FIG. 19.

One difference between the PHY 2002 of FIG. 20 and the PHY 1902 of FIG.19 is in the number ETHERNET ports supported. The PHY 2002 of FIG. 20supports a single ETHERNET port. Also, the MAC device 2016 of FIG. 20 isa MAC device suitable for use in an end node device such as a computer2000. Likewise, the software 2032 executing on the host processor 2030is software that is typically executed by an end-user computer 2000.

Although FIGS. 19 and 20 illustrate particular examples of howfunctionality for reading media information stored on or in physicalcommunication medium can be integrated into one or more of theintegrated circuits (or other circuits or devices) that communicate overthe communication media, it is to be understood that such media readingfunctionality can be integrated in other ways.

In other embodiments, media information is stored in or onunconnectorized cables or other physical communication media. Forexample, in one such embodiment, storage devices are attached near eachend of the unconnecterized cable so that when each end of the cable isattached to a respective attachment point, an interface for a respectiveone of the storage devices mates with a corresponding media readinginterface located on or near the attachment point so the informationstored in the storage device can be read from the storage device in asimilar manner as is described above. Such embodiments can include punchdown connections for connecting copper twisted pair cables to the rearsides of RJ jacks or to Krone-type blocks that include InsulationDisplacement Connectors (IDC's).

FIG. 21 is a diagram of one embodiment of a jacket 2100 that can befitted around an RJ-45 plug in order to attach a storage device to theRJ-45 plug. The jacket 2100 is formed as a molded, flexible circuit 2102that has two side walls 2104 and a top wall 2106. The flexible circuit2102 is formed from one or more flexible films (for example, one or morepolymer films) and is configured to fit snuggly around an RJ-45 plug sothat the jacket 2100, once placed around the plug, will remain securelyaffixed to the RJ-45 plug.

In the embodiment shown in FIG. 21, a storage device 2108 (for example,an EEPROM or other non-volatile memory device) is mounted on the outersurface of the top wall 2106 of the molded, flexible circuit 2102. Thestorage device interface for mating with a media reading interfacecomprises a set of conductive leads 2110 that are formed on the outersurface of the top wall 2106 and extend down the outer surface of bothside walls 2104. At least a portion of the leads 2110 are exposed (thatis, do not have an insulator formed over them) so that correspondingcontacts from a media reading interface can come into contact with theleads 2110 when the plug around which the jacket 2100 is attached isinserted into a port. In such an embodiment, the contacts of the mediareading interface can be spring-loaded into order to press against theleads 2110 in order to form a good electrical contact. The media readinginterface can then be used to read the information stored in the storagedevice 1508 in the manner described above.

Also, in this embodiment, an infra-red emitter 2112 is mounted on theouter surface of the top wall 2106. The infra-red emitter 2112 isconfigured to emit an infra-red signal on which at least a portion ofthe information stored in the storage device 2108 is encoded. In oneimplementation, the infra-red emitter 2112 is configured to output thisinfra-red signal with the information encoded thereon whenever thestorage device 2108 is read using the media reading interface. Thejacket 2100 is configured so that a technician can position an infra-reddetector near the infra-read emitter 2112 in order to receive theinfra-red signal that is emitted. The infra-red detector can be coupledto, for example, a hand held unit that decodes the received infra-redsignal and displays the information that was encoded on the infra-redsignal. In this way, a technician can view the information that isstored in the storage device 2108 without requiring the RJ-45 plug to beremoved from a port. This embodiment can be adapted for other connectortypes, including fiber optic connectors.

The PLI information that is captured, maintained, and made availableusing the techniques described here can be used for many different typesof applications. For example, the PLI information can be used inmanaging the amount of slack that is associated with each media segmentin the system. When a new patch cord (or other media segment) is neededto be installed in the network, the physical layer information that hasbeen captured can be used to determine a precise and appropriate lengthfor the patch cord based on the PLI and the particular slack-managementpolicies that are used by the enterprise or carrier. Also, such PLI canbe used to assist with public safety applications (for example, to helpto locate devices that are used in a voice-over-Internet Protocol (VOIP)telephony system).

Examples of how such physical layer information can be used include thefollowing. For example, a NMS (or other user interface associated withthe aggregation point 120 or any connector assembly 102 such as patchpanel 302 or 302′), when displaying information about a particularsegment of physical media, can also be configured to automatically sendthe user to a web site via which the user can order a replacement forthat particular media segment. For example, a Web-browser based userinterface can be configured to display a button (or other user interfaceelement) that a user can click on in order to automatically bring up aweb site via which a replacement segment can be ordered. Similarfunctionality can be included in the user interfaces that are displayedby the aggregation points 120 and connector assemblies 104 (for example,by the web servers that execute on the aggregation points 102 and theconnector assemblies 104 (for example, patch panels 302 or 302′)).

In another example, when a particular lot of physical communicationmedia segments is recalled (for example, due to safety or performanceconcerns), the physical layer information that is obtained in the mannerdescribed here can be used to determine if and where any of the recalledsegments of physical media are deployed in the network. This informationcan be used in determining whether to replace the segment and/or can beused in actually replacing the segment.

In another example, the physical layer information described here isused for intrusion detection. For example, for particular secureresources on a network (for example, a particular server or service), asecurity policy can be established that specifies that the secureresources should only be accessed by specific computers that are coupledto the secure resource using particular ports of particularinter-networking devices or other connector assemblies and particularsegments of physical communication media. If someone attempts to accessthe secure resources in a manner that does not comply with the securitypolicy, he or she is not granted access to the secure resources. Forexample, if an intruder were able to spoof the identify of an authorizedcomputer but accessed the secure resource using an unauthorized logicalcommunication link, the intruder would still be denied access to thesecure resource unless the intruder is able to spoof the identities ofall of the other elements identified in the policy (for example, theidentities of all the physical communication media that implement thelogical communication link between the computer and the secureresource).

In another example, the aggregation point receives and store informationabout certain conditions that exist in various locations in which thephysical communication media is deployed. For example, the aggregationpoint can be configured to receive and store information that is uniqueto each location (such as, local requirements concerning the use ofbattery backups, environmental conditions obtained from external sensorsand external systems (such as external temperature sensors, HVACsystems, or computer servers that provide weather related information)).Routing decisions within the network can then be made, at least in part,based on such locally unique conditions.

In another example, a technician near a particular patch panel 302 maywant to swap out a particular patch cord (for example, because a visualinspection of the patch cord identified some potential issue with thepatch cord). A request for clearance to disconnect the patch cord fromthe associated port 304 would be routed to an aggregation point or aNMS. The aggregation point or NMS would send messages to one or morerelevant inter-networking devices 354 indicating that a patch cord usedto implement a particular logical communication link is going to bedisconnected in the near future. The inter-networking devices 354, inresponse to such a signal, would route certain classes of traffic (forexample, real-time traffic such as telephony or multimedia traffic) awayfrom that logical communication link. Also, the inter-networking devices354 can be configured to communicate an “all clear” signal back to theaggregation point or NMS, which indicates that it is okay, from theperspective of each such device, to disconnect the relevant patch cord.When the aggregation point or NMS receives all-clear signals from allthe notified inter-networking devices, the aggregation point or NMSinforms the technician (using the display 315) that it is okay todisconnect that patch cord.

In another example, the physical layer information obtained using thetechniques described here is used to check if a particular type ofphysical communication media has been installed. For example, where anenterprise or carrier wishes to deploy a particular type of physicalcommunication media for a given logical communication link (for example,CAT-6 compatible physical communication media to implement GIGABITETHERNET communication links), the physical layer information that isobtained as described above can be used to confirm that each physicalcommunication media segment of the logical communication link has beenimplemented using the appropriate type of physical communication media.Another example is to confirm that multi-mode fiber or shieldedtwisted-pair cabling has been deployed instead of single-mode fiber orunshielded twisted-pair cabling, respectively, which may not be readilyapparent from a visual inspection of the communication media wheninstalled.

In another example, the physical layer information obtained using thetechniques described here is used for theft monitoring. For example, inthe case of IP telephony, the IP telephony server can be configured todeliver telephony service to each IP phone only if that IP phone is usedwith particular logical communication links implemented using particularphysical layer elements (for example, segments deployed within a givenbuilding). If the IP phone is stolen or moved outside of any authorizedarea, the IP telephony server does not provide service to the IP phone,even if it is able to access the IP telephony server.

The techniques described here can be used in a variety of applications,including enterprise applications and carrier applications.

FIGS. 22 and 23 illustrate one example of a carrier application.

FIG. 22 illustrates a network 2200 deploying passive fiber optic lines.As shown, the network 2200 can include a central office 2201 thatconnects a number of end subscribers 2205 (also called end users 2205herein) in a network. The central office 2201 can additionally connectto a larger network such as the Internet (not shown) and a publicswitched telephone network (PSTN). The network 2200 can also includefiber distribution hubs (FDHs) 2203 having one or more optical splitters(for example, 1-to-8 splitters, 1-to-16 splitters, or 1-to-32 splitters)that generate a number of individual fibers that may lead to thepremises of an end user 2205. The various lines of the network 2200 canbe aerial or housed within underground conduits.

The portion of the network 2200 that is closest to central office 2201is generally referred to as the F1 region, where F1 is the “feederfiber” from the central office 2201. The portion of the network 2200closest to the end users 2205 can be referred to as an F2 portion ofnetwork 2200. The network 2200 includes a plurality of break-outlocations 2202 at which branch cables are separated out from the maincable lines. Branch cables are often connected to drop terminals 2204that include connector interfaces for facilitating coupling of thefibers of the branch cables to a plurality of different subscriberlocations 2205.

Splitters used in an FDH 2203 can accept a feeder cable F1 having anumber of fibers and may split those incoming fibers into, for example,216 to 432 individual distribution fibers that may be associated with alike number of end user locations. In typical applications, an opticalsplitter is provided prepackaged in an optical splitter module housingand provided with a splitter output in pigtails that extend from themodule. The splitter output pigtails are typically connectorized with,for example, SC, LC, or LX.5 connectors. The optical splitter moduleprovides protective packaging for the optical splitter components in thehousing and thus provides for easy handling for otherwise fragilesplitter components. This modular approach allows optical splittermodules to be added incrementally to FDHs 2203 as required.

FIG. 23 is a schematic diagram showing an example cable routing schemefor the FDH 2203.

The FDH 2203 generally administers connections at a termination panelbetween incoming fiber and outgoing fiber in an Outside Plant (OSP)environment. As the term is used herein, “a connection” between fibersincludes both direct and indirect connections. Examples of incomingfibers include the feeder cable fibers that enter the cabinet andintermediate fibers (for example, connectorized pigtails extending fromsplitters and patching fibers/jumpers) that connect the feeder cablefiber to the termination panel. Examples of outgoing fibers include thesubscriber cable fibers that exit the cabinet and any intermediatefibers that connect the subscriber cable fibers to the terminationpanel. The FDH 2203 provides an interconnect interface for opticaltransmission signals at a location in the network where operationalaccess and reconfiguration are desired. For example, as noted above, theFDH 2203 can be used to split the feeder cables and terminate the splitfeeder cables to distribution cables routed to subscriber locations. Inaddition, the FDH 2203 is designed to accommodate a range of alternativesizes and fiber counts and support factory installation of pigtails,fanouts and splitters.

As shown at FIG. 23, a feeder cable 2320 is initially routed into theFDH 2203 through a cabinet 2302. In certain embodiments, the fibers ofthe feeder cable 2320 can include ribbon fibers. An example feeder cable2320 may include twelve to forty-eight individual fibers connected to aservice provider central office 2201. In some embodiments, afterentering the cabinet 2302, the fibers of the feeder cable 2320 arerouted to a feeder cable interface 2338 (for example, fiber opticadapter modules, a splice tray, etc.). At the feeder cable interface2338, one or more of the fibers of the feeder cable 2320 areindividually connected to separate splitter input fibers 2324. Thesplitter input fibers 2324 are routed from the feeder cable interface2338 to the splitter module housing 2308. At the splitter module housing2308, the splitter input fibers 2324 are connected to separate splittermodules 2316, wherein the input fibers 2324 are each split into multiplepigtails 2326, each having connectorized ends 2328. In otherembodiments, however, the fibers of the feeder cable 2320 can beconnectorized and can be routed directly to the splitter modules 2316thereby bypassing or eliminating the need for an intermediate feedercable interface 2338.

When the pigtails 2326 are not in service, the connectorized ends 2328can be temporarily stored on a storage module 2318 that is mounted atthe storage region 2306 of the cabinet 2302. When the pigtails 2326 areneeded for service, the pigtails 2326 are routed from the splittermodules 2316 to a termination module 2310 that is provided at thetermination region 2304 of the cabinet 2302. At the termination module2310, the pigtails 2326 are connected to the fibers of a distributioncable 2330. The termination panel is the dividing line between theincoming fibers and the outgoing fibers. A typical distribution cable2330 forms the F2 portion of a network (see FIG. 22) and typicallyincludes a plurality of fibers (for example, 144, 216 or 432 fibers)that are routed from the FDH 2203 to subscriber locations 2205. Cables2330 with connectorized ends 2332 connect to the connectorized ends 2328of the pigtails 2326 at fiber optic adapters 2312.

In some embodiments, one or more of the fibers of the feeder cable 2320are not connected to any of the splitter modules 2316. Rather, thesefibers of the feeder cable 2320 are connected to pass-through fibers2334 having connectorized ends 2336. The pass-through fibers 2334 areconnected to the termination modules 2310, without first connecting tothe splitter modules 2316. By refraining from splitting a fiber 2334, astronger signal can be sent to one of the subscribers. The connectorizedends 2336 of the pass-through fibers 2334 can be stored at the storageregion 2306 when not in use. Cables 2330 with connectorized ends 2332connect to the connectorized ends 2336 of the pass-through fibers 2334at the fiber optic adapters 2312. The feeder interface device 2338includes connections 2322 for connecting the various cables, such aswith splices or connectorized ends and adapters like connectorized ends2328 and 2336 and adapters 2312 noted above.

The various segments of physical communication media that are used inthe network 2200 of FIGS. 22-23 can have identifier and attributeinformation stored in or on them. For example, the various connectorizedfibers described above in connection with FIGS. 22-23 can be outfittedwith storage devices and the corresponding termination modules (andother attachment points) can include corresponding media readinginterfaces to read at least a portion of the identifier and attributeinformation stored in each of the storage devices. The identifier andattribute information that is read from the storage devices can becommunicated to an aggregation point for use as described herein (usinga suitable communication link such as a wireless or wired communicationlink). Other physical layer information (for example, information aboutthe termination modules, spliters, cabinets, and other devices in thenetwork and information about the locations in which they are deployed)can also be provided to such an aggregation point for use thereby.

In another example, the physical layer information obtained using thetechniques described here is used by a telecommunications carrier toassist fulfilling service level agreements. For example, as noted above,the physical layer information can be used to determine if a givenlogical communication link has been implemented using appropriatephysical communication media (for example, CAT-6 cabling in ETHERNET inthe First Mile (EFM) applications or the appropriate type of fiber).This may be especially important at the demarcation point between thetelecommunication carrier's equipment and the customer's equipment.Also, physical layer information can be used to determine ifunauthorized changes have been made at the demarcation point.

In another example, the physical layer information obtained using thetechniques described here is used by a telecommunications carrier toimplement differentiated service levels. For example, where certaincustomers require their communications traffic to travel through certaingeographic regions (for example, to comply with export control laws), acarrier can use the physical layer information obtained using thetechniques described here to route the customers' traffic in compliancewith the customers' requirements. In another example, each routingpoint, site, building, etc. is assigned a security score, and certaincommunication traffic is routed only through routing points, sites,buildings, etc. that have a security score at or above a certain level.

A number of embodiments of the invention defined by the following claimshave been described. Nevertheless, it will be understood that variousmodifications to the described embodiments may be made without departingfrom the spirit and scope of the claimed invention. Accordingly, otherembodiments are within the scope of the following claims.

What is claimed is:
 1. A system comprising: a plurality of patch panels,each of the patch panels comprising a plurality of ports, wherein eachof the patch panels is configured to read cable information stored instorage devices associated with connected attached to cables that areconnected to the ports of the respective patch panel; an aggregationpoint communicatively coupled to the plurality of patch panels, whereineach of the patch panels is configured to send at least some of thecable information read from the storage device associated with theconnectors attached to the cables that are connected to the ports of therespective patch panel to the aggregation point and wherein theaggregation point is configured to receive the cable information sent bythe patch panels and wherein the aggregation point is configured tostore at least some of the cable information sent by the patch panels tothe aggregation point; and a network management system (NMS) that iscommunicatively coupled to the aggregation point, wherein the NMS isconfigured to receive at least a portion of the cable information thatis read from the storage devices associated with the connectors attachedto the cables that are connected to the ports of the patch panels andstored by the aggregation point and wherein the NMS is configured to useat least some of the cable information received from the aggregationpoint in performing a network management function; and wherein theaggregation point is configured to automatically discover the patchpanels and cause each of the patch panels to send to the aggregationpoint at least some of the cable information read from the storagedevices associated with the connectors attached to the cables that areconnected to the ports of the respective patch panels.
 2. The system ofclaim 1, wherein the NMS displays a graphical representation of anetwork, wherein the graphical representation shows at least one logicalcommunication link between network elements; and wherein the NMS isconfigured to display various physical layer items that implement thatlogical communication link using at least some of the cable informationreceived from the aggregation point.
 3. The system of claim 1, whereinthe NMS is configured to carry out guided moves, adds, and changes ofcabling using the cable information read from a storage deviceassociated with a connector attached to the involved cable.
 4. Thesystem of claim 1, wherein the NMS is configured to receive the cableinformation from the aggregation point using at least one of the SimpleObject Access Protocol (SOAP) and the Simple Network Management Protocol(SNMP).
 5. The system of claim 1, wherein the aggregation pointcomprises middleware that provides an application programming interface(API) by which the NMS is able to access at least some of the cableinformation stored by the aggregation point.
 6. The system of claim 1,wherein the patch panels comprise at least one of a fibre-optic patchpanel and copper-cable patch panel.
 7. The system of claim 1, whereinthe patch panels comprises at least one of a fiber splice panel and afiber splice tray.
 8. The system of claim 1, wherein the cableinformation comprises information about the respective connectorattached to one or more of the cables.
 9. The system of claim 1, whereinthe cable information comprises information related to at least one ofan identifier that uniquely identifies one or more the cables, a partnumber associated with one or more of the cables, a connector typeassociated with one or more of the cables, a media type associated withone or more of the cables, a length associated with one or more of thecables, a serial number associated with one or more of the cables, acable polarity, a date of manufacture associated with one or more of thecables, a manufacturing lot number associated with one or more of thecables, a visual attribute associated with one or more of the cables, avisual attribute associated with the respective connector attached toone or more of the cables, an insertion count associated with one ormore of the cables, an Enterprise Resource Planning system, test dataassociated with one or more of the cables, media quality data associatedwith one or more of the cables, and performance data associated with oneor more of the cables.
 10. The system of claim 1, wherein theaggregation point is further configured to receive and store at leastone of: information about the patch panels; information about a layoutof one or more buildings in which the patch panels are deployed;information about locations of the patch panels or the cables;information about end-user devices; information about the location of avoice-over-internet-protocol telephony device; information that ismanually entered and uploaded to the aggregation point; and informationabout local conditions and requirements associated with each of thepatch panels.
 11. The system of claim 1, wherein the aggregation pointis further configured to receive and store at least one of informationabout the compliance of one or more components with one or morespecifications, information about the compliance of a permanent linkwith one or more specifications, and information about the compliance ofa channel with one or more specifications.
 12. The system of claim 1,wherein each storage device comprises non-volatile memory.
 13. Thesystem of claim 1, wherein the cables comprise at least one of a coppercabling or an optical fiber cabling.
 14. The system of claim 1, whereinthe cables comprise at least one metallic cable.
 15. The system of claim1, wherein the cables comprises at least one fiber optic cable.
 16. Thesystem of claim 1, wherein at least one of the cables is used toimplement at least a portion of a logical communication link.
 17. Thesystem of claim 1, wherein at least one of the cables is used toimplement logical communication links.
 18. The system of claim 1,wherein the ports of the patch panels are configured to connect toconnectors attached to cables to implement portions of logicalcommunication links.
 19. The system of claim 14, wherein the metalliccable includes an RJ-45 modular jack connected to at least one end. 20.The system of claim 15, wherein the fiber optic cable includes an LCconnector, an SC connector, an ST connector, or an MPO connectorconnected to at least one end thereof.